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

Fortinet FortiOS Heap-Based Buffer Overflow Vulnerability (CVE-2022-42475)

Multiple versions of Fortinet FortiOS SSL-VPN contain a heap-based buffer overflow vulnerability which can allow an unauthenticated, remote attacker to execute arbitrary code or commands via specifically crafted requests.

Published Jan 2, 2023 · 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. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2023-01-03 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-197) (CWE-197) vulnerability in Fortinet FortiOS. A heap-based buffer overflow vulnerability [CWE-122] in FortiOS SSL-VPN 7.2.0 through 7.2.2, 7.0.0 through 7.0.8, 6.4.0 through 6.4.10, 6.2.0 through 6.2.11, 6.0.15 and earlier and FortiProxy SSL-VPN 7.2.0 through 7.2.1, 7.0.7 and earlier may allow a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests. 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 fortios: 5.0.0 ≤ v ≤ 5.0.14, 5.2.0 ≤ v ≤ 5.2.15, 5.4.0 ≤ v ≤ 5.4.13, 5.6.0 ≤ v ≤ 5.6.14, 6.0.0 ≤ v < 6.0.16, 6.2.0 ≤ v < 6.2.12, 6.4.0 ≤ v < 6.4.11, 7.0.0 ≤ v < 7.0.9, 7.2.0 ≤ v < 7.2.3, 6.0.0 ≤ v < 6.0.15, 6.4.0 ≤ v < 6.4.10, 7.0.0 ≤ v < 7.0.8; fortiproxy: 1.0.0 ≤ v ≤ 1.0.7, 1.1.0 ≤ v ≤ 1.1.6, 1.2.0 ≤ v ≤ 1.2.13, 2.0.0 ≤ v < 2.0.12, 7.0.0 ≤ v < 7.0.8, 7.2.0 ≤ v < 7.2.2
Real-world incidentsWhat we've seen

Used in known ransomware campaigns. Threat-research write-up: https://fortiguard.com/psirt/FG-IR-22-398

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-2022-42475'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-2022-42475↗ MSRC Advisory↗ NVD↗ Vendor Advisory