LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24005: Usage of hard-coded cryptographic keys to encrypt configuration files and debug logs in FortiAuthenticator...

Usage of hard-coded cryptographic keys to encrypt configuration files and debug logs in FortiAuthenticator versions before 6.3.0 may allow an attacker with access to the files or the CLI configuration to decrypt the sensitive data, via knowledge of the hard-coded key.

MediumCVSS 4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

FortiAuthenticator before 6.3.0 used hard-coded cryptographic keys for encrypted configuration files and debug logs. If someone can obtain those files or CLI configuration output, they may decrypt sensitive data that administrators expected to remain protected.

Executive priority

Treat this as a moderate confidentiality risk. It is unlikely to be internet-exploitable by itself, but exposed configuration or log files can reveal sensitive operational data. Prioritize upgrade and cleanup where FortiAuthenticator stores identity or access-control secrets.

Technical view

CVE-2021-24005 is a confidentiality issue in Fortinet FortiAuthenticator versions before 6.3.0. The CVE describes hard-coded keys used for encrypting configuration files and debug logs, allowing decryption by an attacker with file or CLI configuration access. CVSS 3.1 score is 4.0, local attack vector.

Likely exposure

Exposure is limited to FortiAuthenticator deployments running versions before 6.3.0. Risk is higher where configuration backups, debug logs, or CLI output are accessible to lower-trust users, shared storage, ticket attachments, or compromised administrative workstations.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires access to configuration files, debug logs, or CLI configuration data, plus knowledge of the hard-coded key. The primary impact is disclosure of sensitive data, not integrity or availability loss.

Researcher notes

Evidence is limited to the CVE record and Fortinet advisory reference. The CVSS vector is local with low confidentiality impact. Do not claim remote exploitation or active exploitation from the supplied bundle. Validate exposure through version inventory and sensitive-file handling practices.

Mitigation direction

  • Upgrade FortiAuthenticator to 6.3.0 or later per Fortinet guidance.
  • Review Fortinet advisory FG-IR-20-049 for environment-specific upgrade instructions.
  • Restrict access to configuration backups, debug logs, and CLI exports.
  • Remove old exported configs and debug logs from shared or insecure storage.
  • Rotate credentials or secrets found in exposed files if access is suspected.

Validation and detection

  • Inventory all FortiAuthenticator appliances and confirm their software versions.
  • Flag any FortiAuthenticator instance running a version before 6.3.0.
  • Review storage locations for exported configs, backups, CLI captures, and debug logs.
  • Check access logs for unusual reads or transfers of those sensitive files.
  • Confirm file permissions limit access to authorized administrators only.
Prepared
Confidence
high
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2021-24005 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
Medium
CVSS
4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N2.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4Medium
CVSS 3.1 vector shape for CVE-2021-24005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FortinetFortiAuthenticatorFortiAuthenticator versions before 6.3.0.Listed
Weakness

CWE details

No CWE listed

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