Live › vulnerability › CVE-2019-6693
Go to dashboardFortinet FortiOS contains a hard-coded cryptographic key used to encrypt configuration backup files. An attacker who knows the key can decrypt a backup and read sensitive data stored in it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Fortinet FortiOS | vendor | – | – |
| fortinet fortios | vendor | <= 5.6.10 | – |
| fortinet fortios | vendor | >= 6.0.0, <= 6.0.6 | – |
| fortinet fortios | vendor | = 6.2.0 | – |
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Use of a hard-coded cryptographic key to cipher sensitive data in FortiOS configuration backup file may allow an attacker with access to the backup file to decipher the sensitive data, via knowledge of the hard-coded key. The aforementioned sensitive data includes users' passwords (except the administrator's password), private keys' passphrases and High Availability password (when set).
This page as .md · .json · in your agent: get_signal("CVE-2019-6693")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.