LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29060: A use of hard-coded cryptographic key vulnerability [CWE-321] in FortiDDoS API 5.5.0 through 5.5.1, 5.4.0 t...

A use of hard-coded cryptographic key vulnerability [CWE-321] in FortiDDoS API 5.5.0 through 5.5.1, 5.4.0 through 5.4.2, 5.3.0 through 5.3.1, 5.2.0, 5.1.0 may allow an attacker who managed to retrieve the key from one device to sign JWT tokens for any device.

HighCVSS 8.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FortiDDoS appliances in listed 5.x versions used a hard-coded cryptographic key for API JWT signing. If an attacker obtains that key from one device, they may be able to create trusted tokens for other affected devices, undermining authentication and potentially exposing sensitive control functions.

Executive priority

Treat this as a high-priority FortiDDoS exposure issue. It affects security infrastructure and can undermine API trust if a key is recovered. Prioritize asset identification, vendor-guided upgrade planning, and limiting management/API access while remediation is confirmed.

Technical view

CVE-2022-29060 is a CWE-321 hard-coded cryptographic key issue in the FortiDDoS API. The CVSS 3.1 score is 8.1 high with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact. The stated prerequisite is retrieving the key from one device.

Likely exposure

Exposure is limited to Fortinet FortiDDoS 5.5.0-5.5.1, 5.4.0-5.4.2, 5.3.0-5.3.1, 5.2.0, and 5.1.0. Risk increases where the FortiDDoS API or management interface is reachable from untrusted networks.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked CISA KEV. Exploitation is not described as trivial: the attacker must first retrieve the shared key from one affected device, then could sign JWT tokens for any affected device.

Researcher notes

The key technical constraint is evidence of key retrieval from one device before cross-device JWT signing. The source bundle does not include patch version details or exploit telemetry. Avoid assuming broader Fortinet product impact beyond FortiDDoS versions explicitly listed.

Mitigation direction

  • Check Fortinet advisory FG-IR-22-071 for fixed versions or supported workarounds.
  • Upgrade affected FortiDDoS systems according to Fortinet guidance.
  • Restrict FortiDDoS API and management access to trusted administrative networks.
  • Inventory exposed FortiDDoS interfaces and remove unnecessary internet reachability.
  • Review logs for suspicious API authentication or token activity.

Validation and detection

  • Identify all FortiDDoS appliances and record exact firmware versions.
  • Compare each version against the affected ranges listed for CVE-2022-29060.
  • Confirm whether the FortiDDoS API is reachable from untrusted networks.
  • Verify remediation status against Fortinet advisory FG-IR-22-071.
  • Check authentication logs for unusual API access patterns.
Prepared
Confidence
medium
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-2022-29060 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:X/RL:U/RC:R

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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:X/RL:U/RC:R2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2022-29060Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:X/RL:U/RC:R

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
FortinetFortinet FortiDDoSFortiDDoS 5.5.0 through 5.5.1, 5.4.0 through 5.4.2, 5.3.0 through 5.3.1, 5.2.0, 5.1.0Listed
Weakness

CWE details

No CWE listed

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