dbcve.org
FortiosOperating system · Fortinet

CVE-2024-36504

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.9 / 7.4.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An out-of-bounds read vulnerability [CWE-125] in FortiOS SSLVPN web portal versions 7.4.0 through 7.4.4, versions 7.2.0 through 7.2.8, 7.0 all verisons, and 6.4 all versions may allow an authenticated attacker to perform a denial of service on the SSLVPN web portal via a specially crafted URL.

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

An out-of-bounds read vulnerability (CWE-125) in FortiOS SSLVPN web portal affects versions 7.4.0-7.4.4, 7.2.0-7.2.8, 7.0 all versions, and 6.4 all versions. An authenticated attacker can cause denial of service by sending a specially crafted URL to the SSLVPN web portal.

MitigationApply the vendor-supplied patch or upgrade to a FortiOS version beyond the affected ranges as specified in the Fortinet security advisory.

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
FortiosOperating system
Affected:>= 6.4.0, < 7.2.9>= 7.4.0, < 7.4.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check FortiOS version
    Run the following command in FortiOS CLI: get system status. Alternatively, use ' diagnose sys get MBUF status | grep -i version' or check System > FortiGuard in the web UI.
    Affected if The displayed version falls within 6.4.0-6.4.x, 7.0.x, 7.2.0-7.2.8, or 7.4.0-7.4.4.
  2. Verify SSLVPN web portal is enabled
    Run the following command in FortiOS CLI: get vpn ssl settings. Alternatively, navigate to VPN > SSL-VPN Settings in the web UI and check if SSL-VPN is enabled.
    Affected if SSLVPN web portal is enabled and the FortiOS version is in the affected range.
  3. Confirm SSLVPN web portal configuration
    Run the following command in FortiOS CLI: get vpn ssl web portal. This displays the configured web portal profiles.
    Affected if Any web portal profile exists and the FortiOS version is in the affected range.

A system is affected if it runs FortiOS version 6.4.0 or higher but below 7.2.9, or version 7.4.0 or higher but below 7.4.5, and has SSLVPN web portal enabled.

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 7.2.9 / 7.4.5 or later
Fixed in 7.2.97.4.5
Interim mitigation

Apply the vendor-supplied patch or upgrade to a FortiOS version beyond the affected ranges as specified in the Fortinet security advisory.

Recommended fix High confidence

FortiOS 7.2.9 (or later) for 7.2 branch; FortiOS 7.4.5 (or later) for 7.4 branch; and latest stable version for 7.0/6.4 branches.

  1. Log in to the FortiOS GUI or CLI with an administrator account.
  2. Check the current firmware version: in CLI run 'get system status', or in GUI look at the dashboard.
  3. Download the fixed firmware image from the Fortinet Support portal: FortiOS 7.2.9 (or later) for the 7.2 branch, FortiOS 7.4.5 (or later) for the 7.4 branch, or the latest stable release for 7.0/6.4 branches.
  4. Back up the current configuration using the GUI 'Backup' or CLI 'execute backup config' command.
  5. Upload the new firmware: in GUI go to System > Firmware, click 'Upload Firmware', select the image, and install; in CLI use 'execute firmware upgrade <image>'.
  6. Reboot the device after installation (GUI will prompt, or CLI 'execute reboot').
  7. After reboot, verify the new version with 'get system status' and confirm the vulnerability is resolved.
Caveat Review the release notes for the target version; some configuration or feature changes may require adjustments after upgrade.

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36504 — 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-36504 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