CVE-2022-29060Network attack vector

Unauthenticated API access via shared JWT signing key

Published Jul 18, 2022 · Updated Oct 25, 2024

Use of a hard-coded key in the Fortinet FortiDDoS API allows remote attackers to forge JWT tokens accepted by affected devices. The API relies on the same embedded signing key across affected 5.1.0, 5.2.0, 5.3.0 through 5.3.1, 5.4.0 through 5.4.2, and 5.5.0 through 5.5.1 releases, so a valid signature is not bound to one appliance. Exploitation requires retrieval of the key from one device and permits token signing for any other device using that key, while Fortinet has not specified the API actions available to the forged token.

CVSS severity8.1
High
EPSS probability0.66%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use of a hard-coded key in the Fortinet FortiDDoS API allows remote attackers to forge JWT tokens accepted by affected devices. The API relies on the same embedded signing key across affected 5.1.0, 5.2.0, 5.3.0 through 5.3.1, 5.4.0 through 5.4.2, and 5.5.0 through 5.5.1 releases, so a valid signature is not bound to one appliance. Exploitation requires retrieval of the key from one device and permits token signing for any other device using that key, while Fortinet has not specified the API actions available to the forged token.

The record

CVE
CVE-2022-29060
Published
Jul 18, 2022
Updated
Oct 25, 2024
Vendor
Fortinet
Product
FortiDDoS
Classifications
CWE-321, T1606
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 18, 2022CVE publishedPublication date reported by the CVE source.
  2. Oct 25, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=FortiDDoS 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

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Fortinet · FortiDDoSversion=FortiDDoS 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

Published CVSS scores

8.1Fortinet, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
T1606Forge Web Credentials

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo