Security Advisory

CVE-2019-6693: FortiOS Hard-Coded Backup Key

Last updated:
  • CVE-2019-6693

CVE-2019-6693 is a hard-coded cryptographic key (CWE-798) in FortiOS that encrypts user passwords, private-key passphrases and the HA password in configuration files and unprotected backups, so anyone holding a leaked config can decrypt them. NVD scores it 6.5. CISA lists it in KEV with known ransomware use. Upgrade to 5.6.11, 6.0.7 or 6.2.1 or later and enable private-data-encryption.

Vulnerability summary

CVSS base score

6.5

Medium severity

EPSS score (FIRST)

6.6%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

Yes

Listed as known exploited

Published

Vulnerability ID: CVE-2019-6693 · Source: NVD

Affected components

ComponentCPEVersion range
Fortinet FortiOS (FortiGate) 5.6 and earliercpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*5.6.10 and below; 5.6.11 and later add the private-data-encryption option, which must be enabled (Fortinet FG-IR-19-007, NVD CPE). The CVE.org CNA record lists 5.6.9 and below
Fortinet FortiOS (FortiGate) 6.0cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*6.0.0 through 6.0.6; 6.0.7 and later add the private-data-encryption option, which must be enabled (Fortinet FG-IR-19-007, NVD CPE). The CVE.org CNA record lists 6.0.5 and below
Fortinet FortiOS (FortiGate) 6.2cpe:2.3:o:fortinet:fortios:6.2.0:*:*:*:*:*:*:*6.2.0; 6.2.1 and later add the private-data-encryption option, which must be enabled (Fortinet FG-IR-19-007, NVD CPE). FIPS-CC devices are not affected per Fortinet

What does this mean for affected devices?

NVD carries Fortinet's description: 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 data covers users' passwords (except the administrator's password), private-key passphrases and the High Availability password. NVD's Primary score is CVSS v3.1 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and CISA ADP gives the same 6.5. Both list CWE-798 (use of hard-coded credentials). The record was published on 2019-11-21 by Fortinet as CNA (NVD, CVE record).

What does the hard-coded key expose on a FortiGate?

Fortinet's PSIRT advisory FG-IR-19-007, titled "Hardcoded symmetric key in fips.c", says the key protects every credential of type "ENC" in the FortiOS CLI configuration except the administrator's password. If the CLI configuration is exposed, for example "willingly posted on a forum for troubleshooting purpose", the ENC values can be decrypted to plaintext, and "same goes for the system backup file, if it is not password protected." One key in every unit means one leaked config is enough: VPN user passwords, certificate passphrases and the HA cluster password come out in clear. The same advisory adds CVE-2020-9289 for FortiManager 6.2.4 and below and FortiAnalyzer 6.2.3 and below. Fortinet rates the FortiOS issue Medium, CVSS 4.3, and notes that FIPS-CC devices are not affected because the encryption method is overridden.

Which FortiOS versions are affected, and what fixes it?

Fortinet lists FortiOS 6.2.0, 6.0.0 to 6.0.6, and 5.6.10 and below, which matches NVD's CPE ranges. The CNA record at CVE.org lists slightly narrower ranges (5.6.9 and below, 6.0.5 and below, 6.2.0), so go by the PSIRT advisory. An upgrade alone does not remove the key: from FortiOS 5.6.11, 6.0.7 and 6.2.1 on, an administrator can set a private key that FortiOS uses instead, and the option is disabled by default:

config system global
  set private-data-encryption enable
end

Fortinet's note warns that enabling it on FortiGates managed by FortiManager or running in HA could cause install errors and split-brain; that was fixed in FortiManager 6.2.7 and FortiGate 6.2.6, 6.4.4 and 6.6.0. The workaround is to password-protect every configuration backup and to treat any ENC value that has been shared as "easy to decrypt", which means rotating those passwords and passphrases. Fortinet's FortiOS 6.4.0 hardening guide shows the same command prompting for a 32-hex-digit private key, says the same key is needed to restore a configuration on another FortiGate and should be used on all units of an HA cluster, and recommends enabling encryption on every backup and sharing only a section of the file with third parties.

Is CVE-2019-6693 exploited?

Yes. CISA added it to the KEV catalog on 2025-06-25 with the required action "Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable", a due date of 2025-07-16, and known ransomware campaign use marked "Known" (catalog version 2026.11.18, as of 2026-11-19). The FortiGuard page still shows "Known Exploited: No" as of 2026-11-19. FIRST EPSS gives it 0.0664, the 94.0th percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).

How does this pattern show up in embedded firmware?

A symmetric key compiled into the binary to protect exported data is one of the hard-coded credential patterns in our guide to fixing hard-coded credentials in embedded firmware. Similar device cases are the shared SSH key in CVE-2022-22722 and the hard-coded SSH and Telnet credentials in CVE-2021-34565. Other KEV-listed FortiOS flaws include CVE-2023-27997, CVE-2024-21762 and CVE-2025-61624.

How to fix this class of issueThis advisory's weakness class is Hard-coded credentials. Our practical guide covers how to detect, fix, verify and disclose it: How to fix hard-coded credentials in embedded firmware.

Evidence

  • NVD: hard-coded cryptographic key ciphers sensitive data in FortiOS configuration backup file; data includes users' passwords (except administrator), private keys' passphrases and HA password; NVD Primary CVSS v3.1 6.5 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; CISA ADP 6.5 same vector; CWE-798 from both; CPE FortiOS <=5.6.10, 6.0.0-6.0.6, 6.2.0; published 2019-11-21; status Analyzed. — NVD
  • Fortinet FG-IR-19-007 'Hardcoded symmetric key in fips.c': affects FortiOS 6.2.0, 6.0.0 to 6.0.6, 5.6.10 and below (all ENC credential data except the administrator's password); CVE-2020-9289 for FortiManager 6.2.4 and below and FortiAnalyzer 6.2.3 and below; FortiOS 5.6.11, 6.0.7, 6.2.1 and above offer 'set private-data-encryption enable' (disabled by default); workaround password-protect backups and avoid exposing configuration; HA/FortiManager caveat fixed in FortiManager 6.2.7 and FortiGate 6.2.6, 6.4.4, 6.6.0; FIPS-CC devices not impacted; Severity Medium, CVSSv3 4.3; page field 'Known Exploited: No'; revision history 2019-11-19 to 2024-02-22. — Fortinet PSIRT
  • Fortinet Hardening your FortiGate 6.4.0, Building security into FortiOS: passwords and certificate private keys are encrypted with a predefined private key by default; 'set private-data-encryption enable' prompts for a 32-hex-digit custom key; the key is required on other FortiGates to restore a configuration and should be the same on all HA units; enable encryption when backing up and share only a section of the file. — Fortinet Document Library
  • CVE record: state PUBLISHED, CNA Fortinet, published 2019-11-21; affected FortiGate 5.6.9 and below, 6.0.5 and below, 6.2.0; CISA ADP Vulnrichment container present. — CVE.org
  • In the CISA KEV catalog version 2026.11.18 (1,786 entries): Fortinet FortiOS Use of Hard-Coded Credentials Vulnerability, dateAdded 2025-06-25, required action apply mitigations per vendor instructions or discontinue use, dueDate 2025-07-16, knownRansomwareCampaignUse Known, CWE-798; checked 2026-11-19. — CISA KEV
  • EPSS 0.0664, percentile 0.94000, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Fortinet PSIRT FG-IR-19-007: Hardcoded symmetric key in fips.c
  3. Fortinet Document Library: Building security into FortiOS (Hardening your FortiGate 6.4.0)
  4. CVE.org record CVE-2019-6693 (CNA: Fortinet)
  5. CISA KEV
  6. FIRST EPSS

Frequently asked questions

Which FortiOS versions fix CVE-2019-6693?

FortiOS 5.6.11, 6.0.7 and 6.2.1 and later let an administrator replace the hard-coded key with a private one, but only after running 'config system global', 'set private-data-encryption enable', 'end'; the option is disabled by default. Affected: 6.2.0, 6.0.0 to 6.0.6 and 5.6.10 and below (per Fortinet FG-IR-19-007).

What data can an attacker decrypt with CVE-2019-6693?

Every ENC-type credential in the FortiOS CLI configuration except the administrator's password: users' passwords, private-key passphrases and the High Availability password. It needs a copy of the configuration or an unprotected backup file (per NVD and Fortinet FG-IR-19-007).

Is CVE-2019-6693 in the CISA KEV catalog?

Yes. CISA added it on 2025-06-25 with a due date of 2025-07-16 and marks known ransomware campaign use as Known (catalog version 2026.11.18, as of 2026-11-19). FIRST EPSS gives it 0.0664, the 94.0th percentile, in the 2026-11-18 dataset.

What should I do if a FortiGate configuration file was shared or leaked?

Fortinet says exposed ENC data should be considered easy to decrypt, so rotate the user passwords, certificate passphrases and HA password it contained, enable private-data-encryption on a fixed version, and password-protect every future configuration backup (per Fortinet FG-IR-19-007).