CVE-2022-29060

8.1 HIGH

📋 TL;DR

This vulnerability involves hard-coded cryptographic keys in FortiDDoS API versions 5.5.0 through 5.5.1, 5.4.0 through 5.4.2, 5.3.0 through 5.3.1, 5.2.0, and 5.1.0. An attacker who obtains the key from one device can forge JWT tokens to impersonate any device, potentially gaining unauthorized access to the API. Organizations using affected FortiDDoS versions are at risk.

💻 Affected Systems

Products:
  • FortiDDoS
Versions: 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
Operating Systems: FortiDDoS OS
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker gains full administrative control over the FortiDDoS system, allowing them to disable DDoS protection, modify configurations, exfiltrate sensitive data, or use the device as a pivot point into the network.

🟠

Likely Case

Attackers forge JWT tokens to bypass authentication and gain unauthorized API access, potentially extracting configuration data or disrupting DDoS protection services.

🟢

If Mitigated

With proper network segmentation and API access controls, impact is limited to the FortiDDoS management interface without lateral movement into the broader network.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires obtaining the hard-coded key first, which may involve other vulnerabilities or access to a compromised device.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: FortiDDoS 5.5.2, 5.4.3, 5.3.2, 5.2.1, 5.1.1

Vendor Advisory: https://fortiguard.com/psirt/FG-IR-22-071

Restart Required: Yes

Instructions:

1. Download the appropriate firmware version from Fortinet support portal. 2. Backup current configuration. 3. Apply firmware update via web interface or CLI. 4. Reboot the device. 5. Verify the update was successful.

🔧 Temporary Workarounds

Restrict API Access

all

Limit network access to the FortiDDoS API interface to only trusted management IP addresses.

Configure firewall rules to restrict access to FortiDDoS management IP/port

Disable Unused API Features

all

Disable any API endpoints or features that are not required for operations.

Review and disable unnecessary API services in FortiDDoS configuration

🧯 If You Can't Patch

  • Isolate FortiDDoS management interface on a separate VLAN with strict access controls.
  • Implement network monitoring for unusual API authentication patterns or JWT token usage.

🔍 How to Verify

Check if Vulnerable:

Check FortiDDoS firmware version via web interface (System > Dashboard) or CLI command 'get system status'.

Check Version:

get system status

Verify Fix Applied:

Verify firmware version is 5.5.2, 5.4.3, 5.3.2, 5.2.1, or 5.1.1 or later.

📡 Detection & Monitoring

Log Indicators:

  • Failed JWT token validations
  • Unusual API authentication patterns
  • API access from unexpected IP addresses

Network Indicators:

  • Unusual traffic to FortiDDoS management interface
  • API requests with forged JWT tokens

SIEM Query:

source="fortiddos" AND (event_type="authentication_failure" OR api_access="unusual")

🔗 References

📤 Share & Export