Security readout for executives and security teams
Plain-English summary
Affected FortiGate backups protect sensitive secrets with a hard-coded cryptographic key. Anyone who obtains a vulnerable backup and knows that key may recover user passwords, private-key passphrases, and the High Availability password. The administrator password is excluded from the disclosed exposure.
Executive priority
Prioritize remediation because CISA confirms known exploitation and exposed backups may disclose reusable credentials. Immediately identify affected appliances and backup locations, restrict access, follow Fortinet guidance, and rotate potentially compromised secrets. Internet exposure alone does not prove vulnerability exploitation.
Technical view
CVE-2019-6693 is CWE-798 in FortiOS configuration-backup encryption. Listed affected releases are 5.6.9 and earlier, 6.0.5 and earlier, and 6.2.0. Exploitation requires access to a backup file and knowledge of the embedded key. CVSS 3.1 is 6.5, reflecting high confidentiality impact without integrity or availability impact.
Likely exposure
Exposure is concentrated where affected FortiGate versions are used and configuration backups can be obtained through weak storage controls, compromised accounts, shared repositories, or prior leakage. The supplied evidence does not identify which environments possess accessible backups.
Exploitation context
CISA lists CVE-2019-6693 in its Known Exploited Vulnerabilities catalog, supporting confirmed exploitation in the wild. The supplied sources do not describe campaign scope, victims, timing, or attacker methods. Possession of a vulnerable backup file remains a necessary condition described by the CVE.
Researcher notes
The weakness concerns confidentiality of encrypted configuration-backup fields, not direct administrator-password recovery or device takeover. CVSS indicates network reachability and low privileges, while the description specifically requires backup-file access. The bundle does not establish how attackers acquire backups or whether recovered secrets remain valid.
Mitigation direction
- Check Fortinet's advisory and move affected appliances to a vendor-supported, non-affected release.
- Restrict, inventory, and monitor access to all FortiOS configuration backups.
- Replace vulnerable historical backups after remediation where operationally feasible.
- Rotate credentials and passphrases contained in backups that may have been exposed.
- Investigate unexpected access to backup repositories and administrative systems.
Validation and detection
- Record each FortiGate's FortiOS version and compare it with the listed affected releases.
- Locate configuration backups across repositories, shares, ticketing systems, email, and administrator devices.
- Review backup access logs for unauthorized downloads or unusual account activity.
- Confirm remediation status against Fortinet's advisory rather than assuming encryption is corrected.
- Verify rotation of potentially exposed user, private-key, and High Availability secrets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-6693 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2019-6693 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2025-06-25T00:00:00.000Z: CVE-2019-6693 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- https://fortiguard.com/advisory/FG-IR-19-007CVE reference, fortinet · x_refsource_CONFIRM
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-6693CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.