# CVE-2022-29060: Hardcoded credentials in Fortinet FortiDDoS

> An attacker can sign JWT tokens for any device by retrieving a hard-coded cryptographic key, bypassing authentication in FortiDDoS.

- **Severity:** High 8.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2022
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-vgx6-62w9-6xwh

## What is CVE-2022-29060?

CVE-2022-29060 is a high-severity vulnerability in Fortinet FortiDDoS, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-29060?

It affects 1 product.


Products: Fortinet Fortiddos.

## How do I fix CVE-2022-29060?

No fix has been published for CVE-2022-29060 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-29060 being exploited?

There is no known exploitation of CVE-2022-29060 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet FortiDDoS

- [CVE-2022-27486](https://insights.sbomify.com/CVE-2022-27486/): Command injection in FortiDDoS (medium 5.9)
- [CVE-2021-24008](https://insights.sbomify.com/CVE-2021-24008/): Information disclosure in FortiDDoS (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29060 and fix it if it is affected.

What it is: CVE-2022-29060 is a high-severity vulnerability in Fortinet FortiDDoS, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29060 in the wild and no public exploit code.

Affected product: Fortinet FortiDDoS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29060/ (Markdown: https://insights.sbomify.com/CVE-2022-29060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29060
- OSV: https://osv.dev/vulnerability/CVE-2022-29060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29060/
Summaries are generated and may contain mistakes; the official description above is the record.