Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-6693: Hard-coded encryption key in Fortinet configuration secrets

Published Nov 21, 2019 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS6.5Medium · v3.1
EPSS6.6%94th percentile
CISA KEVYesAdded Jun 25, 2025
In the wildActivePer CISA KEV
Vendor
Fortinet
IdentifiersCVE-2019-6693CWE-321

CVE-2019-6693 is a hard-coded cryptographic key vulnerability affecting sensitive configuration data in Fortinet FortiOS, FortiManager, and FortiAnalyzer. An attacker possessing an affected CLI configuration or configuration backup can use the manufacturer-set encryption key to decrypt protected values offline. Exposed information includes non-administrator user passwords, private-key passphrases, and the High Availability password when configured. The administrator account password is excluded from the described decryptable password values. In FortiOS, retaining the default credential-encryption settings rather than enabling private-data encryption with a custom key leaves these secrets recoverable.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality of secrets stored in an exposed configuration. Recovered VPN or other account credentials can enable unauthorized access, impersonation, and lateral movement where the accounts remain valid and additional authentication controls do not prevent their use. Disclosure of private-key passphrases and High Availability passwords can undermine associated security controls. The vulnerability has been exploited in ransomware-related activity, including operations associated with Akira. It does not independently provide configuration-file retrieval, authentication bypass, or code execution.

Mitigation

If you can’t patch tonight, do this now.

Restrict configuration exports, CLI read access, and backup storage to authorized administrators. Protect backups with strong access controls and encryption independent of the default embedded credential-encryption key. Restrict appliance management interfaces to trusted networks or authorized peers. Enforce multifactor authentication for VPN and perimeter access to reduce the usefulness of recovered passwords, and review authentication activity for misuse of exposed accounts.

Remediation

Patch, then assume compromise.

Follow Fortinet advisory FG-IR-19-007 and apply applicable vendor fixes or configuration changes for the installed product and release. For FortiOS, enable private-data encryption and replace the default credential-encryption key with a custom key using the vendor-supported procedure. Rotate secrets contained in any exposed configuration and replace accessible backup copies with newly generated, appropriately protected backups. Exact affected and fixed version ranges are not available in the supplied information.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
cve-2019-6693This repository provides a Python script (fortigate-decrypt.py) that exploits CVE-2019-6693, a vulnerability in Fortinet FortiOS (FortiGate) devices. The vulnerability allows an attacker with access to configuration files and knowledge of the static encryption key to decrypt user and High Availability (HA) passwords stored in those files. The script requires two input files: 'data.txt' (containing user data from 'show user local') and 'ha_config.txt' (containing HA configuration from 'show system ha'). It uses a hardcoded AES key ('Mary had a littl') to decrypt base64-encoded password fields and prints the decrypted plaintext passwords. The repository includes a README with usage instructions and a .gitignore. The exploit is operational, as it provides working decryption functionality, but it is not weaponized for remote exploitation; it requires prior access to the configuration files.saladandonionrings · Disclosed Dec 8, 2023 · python · localOperationalfortidecrypter-CVE-2019-6693This seven-file repository implements a standalone Python utility for offline recovery of FortiOS configuration secrets associated with CVE-2019-6693. It exploits the legacy ENC format's hardcoded AES key rather than attacking a live device. The visible code contains the key b"Mary had a littl" and an AES-CBC decryption helper. There is no evidence of a shell payload, remote exploitation, exfiltration, or malicious operator-side behavior in the supplied portions. fortidec.py is a thin command-line launcher. pocforti/decrypt.py contains the configuration parser, decryption-related logic, and main processing workflow. Its visible parser tracks nested config/edit blocks, VDOM context, multiline quoted settings, line numbers, and user-group membership, while collecting malformed-configuration warnings. The README documents file and directory input, local-user/admin/TACACS+ selectors, exact object/user filters, section filtering, secret masking, and summaries. Administrator selection does not imply support for cracking administrator password hashes, which the documentation explicitly excludes. pocforti/reporting.py renders table, compact, Markdown, CSV, TSV, JSON, JSONL, and XLSX reports. It sanitizes terminal text and spreadsheet-formula-like values in delimited exports, and builds XLSX files directly using XML and ZIP. Reports can contain sensitive plaintext unless masking is requested. pocforti/__init__.py is a package marker; requirements.txt declares pycryptodomex>=3.18; README.md documents operation and limitations; .gitignore excludes configurations, credentials, reports, and other potentially sensitive artifacts. No runtime network destination, fixed target address, registry key, or fixed input/output filesystem path is shown. Advisory URLs are documentation links, and OpenXML URLs are format identifiers rather than outbound requests. Portions of decrypt.py and reporting.py were truncated, so the complete decryption, input-validation, and output-writing implementations could not be verified. Repository URL, revision, and archive size were not supplied; empty strings and zero represent unavailable metadata.lureprey · Disclosed Nov 7, 2026 · python · file · localOperationalCVE-2019-6693This repository provides a proof-of-concept Python script (fortigate_decrypt.py) that exploits CVE-2019-6693, a vulnerability in Fortinet FortiGate appliances prior to version 6.2.0 (and specific 6.0.x and 5.6.x versions). The script decrypts configuration secrets that are stored using a static AES key. The user supplies a base64-encoded encrypted secret (as found in FortiGate configuration files) as a command-line argument. The script decodes the input, constructs the IV from the first 4 bytes of the ciphertext, and decrypts the remainder using the static key. The decrypted secret is then printed. The repository consists of a README.md explaining the vulnerability and usage, and the Python script itself. No network or remote attack is performed; the exploit is local and requires access to the configuration file.gquere · Disclosed Dec 21, 2021 · python · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetForticlientapplication
FortinetFortiosoperating_system
FAQ

Frequently asked questions

Is CVE-2019-6693 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jun 25, 2025.
Is there a public exploit for CVE-2019-6693?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2019-6693, the earliest disclosed Dec 21, 2021.
Is there a patch for CVE-2019-6693?
Follow Fortinet advisory FG-IR-19-007 and apply applicable vendor fixes or configuration changes for the installed product and release. For FortiOS, enable private-data encryption and replace the default credential-encryption key with a custom key using the vendor-supported procedure.
What products are affected by CVE-2019-6693?
Fortinet Fortios and Fortinet Forticlient.
How severe is CVE-2019-6693?
CVE-2019-6693 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 6.6% (94th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
vulncheck blogNews · Nov 16, 2026Identifying FortiGate Firmware From a Single ClientHello | Blog | VulnCheckListed as a known-exploited FortiOS vulnerability affecting anchor versions for generations 1, 2, and 3. Gen 1 exposure assumes FortiOS 5.4.0. No technical description is provided.Read more ↗group ibNews · Nov 11, 2026Inside The Server: 14 Months of Offensive Cyber Operations Targeting Europe | Group-IB BlogFortiOS stored-secret protection weakness associated with use of a system default encryption key. The report cites it to explain how possession of a device configuration can permit offline recovery of VPN passwords and other secrets. Enabling private data encryption is the stated mitigation; the report does not separately establish exploitation of this CVE by DarkLunnen.Read more ↗group ibNews · Oct 21, 2026Stray Cat, Open Doors: How k0t Wanders Through the Network Edge | Group-IB BlogUse of a publicly known default encryption key permits offline recovery of secrets from obtained FortiGate configurations, including LDAP and Active Directory bind credentials. The report describes exploitation at scale and identifies enabling private-data-encryption with an operator-defined key as the fix; the protection must be explicitly enabled.Read more ↗stairwellNews · Feb 16, 2026Akira: Pulling on the chains of ransomware - StairwellA Fortinet vulnerability that allows attackers to obtain and decrypt password data from vulnerable Fortinet device configurations; it was used as part of a chained exploitation workflow against Fortinet appliances.Read more ↗
+6 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence2Every report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity9Community discussion across Reddit, Mastodon, and other social sources.