Loading vulnerability…
CVE-2020-9289 is a vulnerability in FortiManager and FortiAnalyzer (versions 6.2.3 and below) where a hard-coded cryptographic key is used to encrypt password data in CLI configuration files. An attacker with access to the CLI configuration or backup files can use the known hard-coded key to decrypt sensitive password data.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2020-9289 (and related CVE-2019-6693), affecting Fortinet FortiManager and FortiAnalyzer products. The exploit consists of a single Python script ('cve-2020-9289.py') that decrypts configuration secrets using a hardcoded AES key ('Mary had a littl'). The script expects a base64-encoded encrypted secret as input, extracts the IV from the first 16 bytes, and decrypts the remainder using AES-CBC. The exploit demonstrates the use of a default, hardcoded key in Fortinet products, allowing attackers with access to encrypted configuration data to recover plaintext secrets. The repository also includes a requirements.txt specifying the 'pycryptodomex' library. No network or remote attack vector is present; the exploit is purely local and requires access to exported configuration data.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.