CVE-2022-42475: Fortinet FortiOS Heap-Based Buffer Overflow
Fortinet FortiOS · listed in the CISA catalog of actively exploited vulnerabilities since 2022-12-13.
- CVSS v3.1 (CVE record)
- 9.3
- critical
- EPSS (exploit probability, 30 days)
- 99.4%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2022-12-13
- US federal due date 2023-01-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2022-42475 explained
CVE-2022-42475 is a heap-based buffer overflow in the SSL-VPN component of Fortinet FortiOS and FortiProxy. A remote unauthenticated attacker can execute arbitrary code or commands with specially crafted requests. CISA lists it as known exploited, including known ransomware use, so exposed devices are at high risk.
Impact
An attacker with network access to the SSL-VPN service needs no credentials and no user interaction. The attacker can run arbitrary code or commands on the device, with high impact on confidentiality, integrity and availability. CISA rates it automatable, meaning it can be exploited at scale, with total technical impact, meaning full control of the affected device. Attackers are known to exploit it, including in ransomware campaigns.
Who is affected
FortiOS: ≥ 5.0.0, ≤ 5.0.14, ≥ 5.2.0, ≤ 5.2.15, ≥ 5.4.0, ≤ 5.4.13, ≥ 5.6.0, ≤ 5.6.14, ≥ 6.0.0, ≤ 6.0.15, ≥ 6.2.0, ≤ 6.2.11, ≥ 6.4.0, ≤ 6.4.10 and ≥ 7.0.0, ≤ 7.0.8, plus one more range shown on the page. It is fixed in 6.0.16, 6.2.12, 6.4.11, 7.0.9 and 7.2.3. FortiProxy: ≥ 1.0.0, ≤ 1.0.7, ≥ 1.1.0, ≤ 1.1.6, ≥ 1.2.0, ≤ 1.2.13, ≥ 2.0.0, ≤ 2.0.11, ≥ 7.0.0, ≤ 7.0.7 and ≥ 7.2.0, ≤ 7.2.1. It is fixed in 7.0.8 and 7.2.2, and 2.0.12 is announced but not yet released.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Fortinet FortiProxyAffectedFixed in
- ≥ 1.0.0, ≤ 1.0.7
- ≥ 1.1.0, ≤ 1.1.6
- ≥ 1.2.0, ≤ 1.2.13
- ≥ 2.0.0, ≤ 2.0.11
- ≥ 7.0.0, ≤ 7.0.7
- ≥ 7.2.0, ≤ 7.2.1
- 2.0.12 (upcoming)
- 7.0.8
- 7.2.2
Fixed versions taken from the CNA solution text.
- Fortinet FortiOSAffectedFixed in
- ≥ 5.0.0, ≤ 5.0.14
- ≥ 5.2.0, ≤ 5.2.15
- ≥ 5.4.0, ≤ 5.4.13
- ≥ 5.6.0, ≤ 5.6.14
- ≥ 6.0.0, ≤ 6.0.15
- ≥ 6.2.0, ≤ 6.2.11
- ≥ 6.4.0, ≤ 6.4.10
- ≥ 7.0.0, ≤ 7.0.8
- ≥ 7.2.0, ≤ 7.2.2
- 6.0.16
- 6.2.12
- 6.4.11
- 7.0.9
- 7.2.3
Fixed versions taken from the CNA solution text.
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiProxyFixed versions taken from the CNA solution text. |
|
|
| Fortinet FortiOSFixed versions taken from the CNA solution text. |
|
|
How to fix it
- Update to the fixed version for your product:
- Fortinet FortiProxy: 2.0.12 (upcoming), 7.0.8, 7.2.2
- Fortinet FortiOS: 6.0.16, 6.2.12, 6.4.11, 7.0.9, 7.2.3
- Vendor advisory: fortiguard.com/psirt/FG-IR-22-398
- CISA's deadline for US federal agencies: 2023-01-03 (passed) – a useful benchmark for everyone else, too.
Vendor solution: Please upgrade to FortiOS version 7.2.3 or above Please upgrade to FortiOS version 7.0.9 or above Please upgrade to FortiOS version 6.4.11 or above Please upgrade to FortiOS version 6.2.12 or above Please upgrade to FortiOS version 6.0.16 or above Please upgrade to upcoming FortiOS-6K7K version 7.0.8 or above Please upgrade to FortiOS-6K7K version 6.4.10 or above Please upgrade to FortiOS-6K7K version 6.2.12 or above Please upgrade to FortiOS-6K7K version 6.0.15 or above Please upgrade to FortiProxy version 7.2.2 or above Please upgrade to FortiProxy version 7.0.8 or above Please upgrade to upcoming FortiProxy version 2.0.12 or above
What to do
- Upgrade FortiOS to
6.0.16,6.2.12,6.4.11,7.0.9or7.2.3, as matches your release line. - Upgrade FortiProxy to
7.0.8or7.2.2. Follow the vendor advisory for2.0.12, which is announced but not yet released. - For older affected ranges with no fixed version in the record, follow the vendor advisory and move to a supported fixed release.
- Until patched, restrict or disable SSL-VPN access where possible and keep management interfaces off the internet.
- Check devices for signs of compromise, because attackers, including ransomware operators, are known to exploit this flaw.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-197 Execute unauthorized code or commands
Questions about CVE-2022-42475
- Is CVE-2022-42475 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-12-13 and reports known ransomware use. US federal agencies had a due date of 2023-01-03 to apply updates per vendor instructions.
- Does an attacker need credentials?
- No. A remote attacker needs no authentication and no user interaction. Only network access to the SSL-VPN service is required to execute arbitrary code or commands.
- Which component is vulnerable?
- The SSL-VPN component of FortiOS and FortiProxy is vulnerable. Devices that expose SSL-VPN to untrusted networks face the most risk and should be updated first.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.