LiveActive security incident?Get immediate response
CVE Record

CVE-2020-9289: Use of a hard-coded cryptographic key to encrypt password data in CLI configuration in FortiManager 6.2.3 a...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This weakness means protected passwords in FortiManager and FortiAnalyzer configuration data could be decrypted by someone who already has the CLI configuration or backup file. The issue is most urgent where backups are broadly accessible, stored in shared repositories, or retained without strong access controls.

Executive priority

Treat this as a credential-protection issue, not a remote break-in by itself. Prioritize it where Fortinet management backups may be accessible outside a tightly controlled administrator group or where exposed secrets could unlock broader network control.

Technical view

CVE-2020-9289 describes use of a hard-coded cryptographic key for password data in CLI configuration on FortiManager 6.2.3 and below and FortiAnalyzer 6.2.3 and below. An attacker needs access to CLI configuration or CLI backup data and knowledge of the key to decrypt sensitive values.

Likely exposure

Exposure is likely limited to organizations running affected Fortinet management products and allowing access to CLI configuration or backup files. Risk increases if backups are shared with administrators, stored outside secured vaults, copied to tickets, or retained in unmanaged locations.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack requires prior access to configuration or backup material, so this is mainly a credential disclosure risk after backup exposure, insider access, or adjacent system compromise.

Researcher notes

Evidence is limited to the CVE description and Fortinet advisory reference in the bundle. No CVSS, CWE, patch version, or exploitation evidence is included here. Avoid assuming remote exploitability; the stated prerequisite is access to CLI configuration or backup data.

Mitigation direction

  • Review Fortinet PSIRT FG-IR-19-007 for official upgrade or remediation guidance.
  • Restrict access to CLI configuration and backup files for affected systems.
  • Rotate passwords or secrets present in exposed configuration backups.
  • Store backups only in encrypted, access-controlled locations.
  • Remove stale backup copies from unmanaged repositories and ticket attachments.

Validation and detection

  • Inventory FortiManager and FortiAnalyzer versions for 6.2.3 or below.
  • Identify all locations where CLI backups are generated, stored, or copied.
  • Review access logs for unexpected configuration or backup file retrieval.
  • Confirm current remediation status against Fortinet PSIRT guidance.
  • Assess whether exposed passwords require rotation after backup access.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Credential 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 lookup
cve · low confidence lookup

CVE-2020-9289 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aFortinet FortiManagerFortiManager 6.2.3 and belowListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.