Attack Simulation & Response

Red TeamEnd-to-end simulation using real adversary tradecraft Blue TeamThreat hunting, monitoring and incident response Purple TeamGrow your offensive and defensive teams together Ransomware Response24/7 emergency response for encrypted systems

Security Testing

Penetration TestingFinding flaws in web, network and mobile applications Enterprise Penetration TestingRegulation-aligned testing for finance and large enterprises Vulnerability ScanningContinuous scanning, prioritised with CVSS
A free scoping call tailored to your organisation.
All services Get a quote

Forensic Threat Hunting

PotreX VestigeHidden threat scanning across disk, memory and forensic traces

Threat Intelligence

PotreX ArgosDark web and leak-focused threat intelligence

Penetration Testing

PotreX BallistaEnterprise penetration testing platform with finding management
Every product can be deployed on-premises or in the cloud.
All products Request a demo
Services
Products
Blog Contact Us Sign In
Home / Blog / CVE-2024-21762
Vulnerability Analysis

FortiOS SSL-VPN: Unauthenticated Memory Write to Device Takeover

Summary

CVE-2024-21762 is an out-of-bounds write in the SSL-VPN component of FortiOS. Specially crafted HTTP requests can reach code execution on the device without any authentication.

A firewall is the most privileged point in the network: compromising it means a direct bridge into internal networks, access to every VPN user identity, and the ability to observe traffic silently. That is why an edge device vulnerability outweighs an application bug with the same CVSS score.

Advisory details

CVECVE-2024-21762
ComponentFortiOS / FortiProxy — SSL-VPN (sslvpnd)
ClassCWE-787 · Out-of-bounds write
SeverityCRITICAL · CVSS 9.8
Affected versionsFortiOS 6.0 – 7.4 builds released before February 2024
PrerequisiteSSL-VPN web mode enabled

Root cause: an untrusted length value

In the SSL-VPN service a length field supplied by the client enters a copy operation without validation, writing past the bounds of the destination buffer. Once the attacker can shape memory layout, that leads to control of execution flow.

On embedded appliances this class of bug is more dangerous than on servers: the system typically revolves around a single privileged process, with limited user separation and fewer modern memory protections.

Version and exposure

analyst@ubuntu: ~/labs/fortinet –□✕
analyst@ubuntu:~/labs/fortinet$ ssh admin@fw.lab.local 'get system status' | grep -E 'Version|Serial-Number'
Version: FortiGate-100F v7.2.6,build1575,230628 (GA.M)
Serial-Number: FG100F3G21xxxxxx

#  below 7.2.7 — affected build

Figure 1 — Reading the device version and build

The second check is whether SSL-VPN web mode is reachable from the internet at all. With the service disabled there is no attack surface for this bug.

analyst@ubuntu: ~/labs/fortinet –□✕
analyst@ubuntu:~/labs/fortinet$ nmap -Pn -p 443,10443 --open fw.lab.local && curl -sk -o /dev/null -w 'login page: %{http_code}\n' https://fw.lab.local/remote/login
PORT      STATE SERVICE
443/tcp   open  https
10443/tcp open  unknown
login page: 200

#  SSL-VPN web mode exposed to the internet

Figure 2 — Confirming the SSL-VPN interface is exposed

Crash logs and traces

Memory corruption attempts rarely land cleanly on the first try; failed attempts show up as service crashes. Lines mentioning sslvpnd in the crash log are a strong indicator.

analyst@ubuntu: ~/labs/fortinet –□✕
analyst@ubuntu:~/labs/fortinet$ ssh admin@fw.lab.local 'diagnose debug crashlog read' | grep -c sslvpnd
17

#  17 sslvpnd crashes — exploitation attempts suspected
#  device isolated, configuration and admin accounts reviewed

Figure 3 — Counting SSL-VPN traces in the crash log

Remediation

The permanent fix is upgrading to the vendor's patched build. Where no maintenance window is available, disabling SSL-VPN web mode is the interim mitigation.

analyst@ubuntu: ~/labs/fortinet –□✕
analyst@ubuntu:~/labs/fortinet$ ssh admin@fw.lab.local 'get system status' | grep Version && nmap -Pn -p 10443 --open fw.lab.local | tail -n 2
Version: FortiGate-100F v7.2.7,build1577,240206 (GA.M)

PORT STATE SERVICE — 10443/tcp closed

#  patched build plus a smaller attack surface

Figure 4 — Verification after upgrading and reducing exposure

  • If the device was internet-facing while unpatched, an upgrade is not enough: admin accounts, local users, VPN tunnels and configuration diffs must all be reviewed.
  • Rotate every VPN user password and any certificates in use.
  • Restrict the management interface to a dedicated management VLAN.

Conclusion

Edge appliances have become the initial access route attackers prefer. Patch management for them should run on a separate, stricter schedule than for servers, and management and VPN surfaces should be kept off the public internet wherever the business allows.

Sources

Test it in your own environment

We assess your internet-facing firewalls and VPN appliances through external attack surface testing.

Call now · 0850 551 01 01 WhatsApp · Send a message Email · info@potrex.com