CASCACascade Atlas

Evidence dossier

CVE-2019-6693

CVE-2019-6693

54.8–76.0Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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).

State
PUBLISHED
Published
Nov 21, 2019
Updated
Oct 21, 2025
Evidence coverage
72%
CISA KEVCatalog member

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

FIRST EPSS5.66%

2026-07-18 · v2026.06.15 · percentile 92.1%

Source stateConflict visible

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

CVEderivative copy
container

CVE Program Container

fortinetoriginal assertion
container

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).

CISA KEVoriginal assertion
observed_exploitation

Fortinet FortiOS Use of Hard-Coded Credentials Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.056630000000; percentile 0.921040000000

Applicability

Cited product scope

Trace impact →
FortinetFortiGate
[{"status": "affected", "version": "5.6.9 and below"}, {"status": "affected", "version": "6.0.5 and below"}, {"status": "affected", "version": "6.2.0"}]unknown
Unknown vendorUnknown product
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*; end including 5.6.10supported
Unknown vendorUnknown product
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*; start including 6.0.0; end including 6.0.6supported
Unknown vendorUnknown product
cpe:2.3:o:fortinet:fortios:6.2.0:*:*:*:*:*:*:*supported

Assessments

CVSS by origin

6.5
nvd@nist.govCVSS 3.1 · role PrimaryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0
nvd@nist.govCVSS 2.0 · role PrimaryAV:N/AC:L/Au:S/C:P/I:N/A:N
6.5
134c704f-9b21-4f2e-91b3-4a467353bcc0CVSS 3.1 · role SecondaryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
6.5
CISA-ADPCVSS 3.1 · role unknownCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.