dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 Feb 2024. Known ransomware use
FortiproxyApplication · Fortinet

CVE-2024-21762

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-09
Fix available
A fix is available. Upgrade to 2.0.14 / 6.0.18 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an out-of-bounds write vulnerability in FortiOS and FortiProxy's SSL-VPN web interface that allows remote attackers to execute arbitrary code or command execution via specially crafted HTTP requests. The memory corruption flaw enables complete system compromise without authentication.

MitigationUpgrade to Fortinet's patched versions (FortiOS 7.4.3+, 7.2.7+, 7.0.14+, 6.4.15+, 6.2.16+, 6.0.18+; FortiProxy 7.4.3+, 7.2.9+, 7.0.15+, 2.0.14+, 1.2.14+, 1.1.7+, 1.0.8+) or disable SSL-VPN functionality if patching is not immediately possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiproxyApplication
Affected:>= 1.0.0, < 2.0.14>= 7.0.0, < 7.0.15>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.3
FortiosOperating system
Affected:>= 6.0.0, < 6.0.18>= 6.2.0, < 6.2.16>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.14>= 7.2.0, < 7.2.7>= 7.4.0, < 7.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and version
    Run 'get system status' via FortiOS/ FortiProxy CLI to display firmware version, build number, and product name
    Affected if The displayed version falls within any of the affected ranges listed in the CVE for FortiOS or FortiProxy
  2. Verify SSL-VPN is enabled
    Run 'get vpn ssl settings' to check if SSL-VPN is currently enabled on the device
    Affected if SSL-VPN status shows as enabled (sslVPN is 'enable' or 'enableful')
  3. Check SSL-VPN listen interface exposure
    Run 'get vpn ssl settings' and review the 'listen-on' or 'bind' interface configuration to identify which interfaces accept SSL-VPN connections
    Affected if SSL-VPN is bound to an interface reachable from untrusted networks such as WAN or port1 with default access
  4. Confirm web interface accessibility
    Run 'get system interface' and review management access settings, or check 'get system admin' for web UI configuration
    Affected if HTTP/HTTPS administrative access is enabled on interfaces exposed to untrusted networks

You are affected if your FortiOS or FortiProxy version falls within any of the listed affected version ranges AND either SSL-VPN or the web management interface is accessible from network segments you do not fully trust.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.14 / 6.0.18 / 6.2.16 or later
Fixed in 2.0.146.0.186.2.16
Interim mitigation

Upgrade to Fortinet's patched versions (FortiOS 7.4.3+, 7.2.7+, 7.0.14+, 6.4.15+, 6.2.16+, 6.0.18+; FortiProxy 7.4.3+, 7.2.9+, 7.0.15+, 2.0.14+, 1.2.14+, 1.1.7+, 1.0.8+) or disable SSL-VPN functionality if patching is not immediately possible.

Recommended fix High confidence

FortiOS: upgrade to 6.0.18, 6.2.16, 6.4.15, 7.0.14, 7.2.7, or 7.4.3 (or later). FortiProxy: upgrade to 2.0.14, 7.0.15, 7.2.9, or 7.4.3 (or later). Choose the nearest version in your current major branch.

  1. 1. Identify the currently installed FortiOS or FortiProxy version by running: get system status (for FortiOS) or get system info (for FortiProxy)
  2. 2. Determine the appropriate upgrade path based on your current major version (6.0.x, 6.2.x, 6.4.x, 7.0.x, 7.2.x, or 7.4.x for FortiOS; 1.x, 2.0.x, 7.0.x, 7.2.x, or 7.4.x for FortiProxy)
  3. 3. Download the corresponding fixed firmware from Fortinet's support portal: https://support.fortinet.com/
  4. 4. Upload the firmware to the Fortinet device via Web UI (System > Firmware) or CLI: execute restore config or execute upgrade firmware
  5. 5. Verify the upgrade completed successfully by checking the system status and confirming the new version number
  6. 6. After upgrade, validate that critical services are functioning normally
Caveat Review Fortinet release notes for your target version for any configuration or feature changes; major version jumps may require careful migration planning

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiproxy Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21762 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data