IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2024-23113|Auth: none — unauthenticated|Reboot: required|Manual only

Fortinet Multiple Products Format String Vulnerability (CVE-2024-23113)

Fortinet FortiOS, FortiPAM, FortiProxy, and FortiWeb contain a format string vulnerability that allows a remote, unauthenticated attacker to execute arbitrary code or commands via specially crafted requests.

Published Feb 15, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2024-10-30 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-134) (CWE-134) vulnerability in Fortinet Multiple Products. A use of externally-controlled format string in Fortinet FortiOS versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.13, FortiProxy versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.8, 7.0.0 through 7.0.14, FortiPAM versions 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiSwitchManager versions 7.2.0 through 7.2.3, 7.0.0 through 7.0.3 allows attacker to execute unauthorized code or commands via specially crafted packets. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Network Security Team
●Firewall Administrators
●IT Security
●Running fortiproxy: 7.0.0 ≤ v ≤ 7.0.14, 7.2.0 ≤ v ≤ 7.2.8, 7.4.0 ≤ v ≤ 7.4.2; fortiswitchmanager: 7.0.0 ≤ v ≤ 7.0.3, 7.2.0 ≤ v ≤ 7.2.3; fortios: 7.0.0 ≤ v ≤ 7.0.13, 7.2.0 ≤ v ≤ 7.2.6, 7.4.0 ≤ v ≤ 7.4.2; fortipam: 1.0.0 ≤ v ≤ 1.0.3, 1.1.0 ≤ v ≤ 1.1.2, 1.2.0
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2024-10-09 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2024-10-30.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2024-23113's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2024-23113↗ MSRC Advisory↗ NVD↗ Vendor Advisory