Skip to content
VulniPulse
Sign in
Advisory severityUnratedFortinet Exploited CISA KEV

Advisory [CVE-2019-6693] FortiGate: 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

This security Fortinet advisory covers CVE-2019-6693 affecting FortiGate.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2019-6693 Source published Source updated

VulniPulse record published

CVE-2019-6693
Affected products & platforms
FortinetFortiGateFirewall
Open source advisory

Android app · Google Play

Monitor future Fortinet CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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

Affected product named by the advisory: FortiGate.

CISA Known Exploited Vulnerability

Listed:
Jun 25, 2025 · federal remediation due Jul 16, 2025
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.
Ransomware use:
Known ransomware campaign use, according to CISA

KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.

Affected versions
  • FortiGate 5.6.9 and below
  • FortiGate 6.0.5 and below
  • FortiGate 6.2.0

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.