Fortinet FortiOS CVE-2019-6693 Hardcoded Cryptographic Key Vulnerability

Risk

Medium

Date Discovered

November 19, 2019

Description

Fortinet FortiOS is prone to a hardcoded cryptographic key vulnerability. Successful exploits will allow attackers to obtain sensitive information that may aid in further attacks. Versions prior to Fortinet FortiOS 5.6.11, 6.0.7 and 6.2.1 are vulnerable.

Technologies Affected

  • Fortinet Fortios 5.6.0
  • Fortinet Fortios 5.6.1
  • Fortinet Fortios 5.6.10
  • Fortinet Fortios 5.6.2
  • Fortinet Fortios 5.6.3
  • Fortinet Fortios 5.6.4
  • Fortinet Fortios 5.6.5
  • Fortinet Fortios 5.6.6
  • Fortinet Fortios 5.6.7
  • Fortinet Fortios 5.6.8
  • Fortinet Fortios 5.6.9
  • Fortinet Fortios 6.0.0
  • Fortinet Fortios 6.0.1
  • Fortinet Fortios 6.0.2
  • Fortinet Fortios 6.0.3
  • Fortinet Fortios 6.0.4
  • Fortinet Fortios 6.0.5
  • Fortinet Fortios 6.0.6
  • Fortinet Fortios 6.2.0

Recommendations

Run all software as a nonprivileged user with minimal access rights.
To limit the impact of latent vulnerabilities, configure database servers and other applications to run as a nonadministrative user with minimal access rights.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from a successful exploit.

Updates are available. Please see the references or vendor advisory for more information.

References

Credits

Bart Dopheide (bart.dopheide@axians.com) and the independent research team Denis Kolegov, Maxim Gorbunov, Nikita Oleksov, Anton Nikolaev.


© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.