dbcve.org
FortiosOperating system · Fortinet

CVE-2024-23662

HIGH · 7.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 7.2.6 / 7.4.2 or later.
See remediation →
84/100
Remediation priority · High
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
An exposure of sensitive information to an unauthorized actor in Fortinet FortiOS at least version at least 7.4.0 through 7.4.1 and 7.2.0 through 7.2.5 and 7.0.0 through 7.0.15 and 6.4.0 through 6.4.15 allows attacker to information disclosure via HTTP 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

FortiOS contains an information disclosure vulnerability where HTTP requests allow unauthorized access to sensitive information. The flaw affects multiple version branches (6.4.x, 7.0.x, 7.2.x, and 7.4.x) and is exploitable via crafted HTTP requests to the web interface or API endpoints.

MitigationApply Fortinet's patches for this vulnerability (consult Fortinet PSIRT for specific fixed versions). Until patched, restrict HTTP/HTTPS access to the FortiOS management interface to trusted management networks only using firewall policies.

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.6>= 7.4.0, < 7.4.2

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
None
Availability
None

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

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 FortiOS version
    Run 'get system status' via CLI or check the web UI dashboard for the firmware version
    Affected if Version matches >= 6.4.0 and < 7.2.6, OR >= 7.4.0 and < 7.4.2
  2. Confirm web interface is enabled
    Check via CLI with 'get system interface' or 'show system interface' to identify management ports, then verify httpd process is running or web-service is enabled in system settings
    Affected if HTTP/HTTPS management service is enabled on any interface
  3. Verify management interface exposure
    Review firewall policy or interface configuration: run 'show system interface' and check which interfaces have 'set management-mode' or are bound to HTTP/HTTPS services, check if any allow external/untrusted access
    Affected if Web interface is reachable from untrusted networks (such as WAN or non-management VLANs)
  4. Check for existing management access restrictions
    Review firewall policies for any explicit denies or restrictions on TCP ports 80/443 for management interfaces, or verify access-list configurations
    Affected if No firewall policy restricts HTTP/HTTPS management access to trusted IP ranges only

The environment is likely affected if FortiOS version falls within the vulnerable ranges AND the web interface/API is accessible over HTTP/HTTPS from untrusted networks.

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.6 / 7.4.2 or later
Fixed in 7.2.67.4.2
Interim mitigation

Apply Fortinet's patches for this vulnerability (consult Fortinet PSIRT for specific fixed versions). Until patched, restrict HTTP/HTTPS access to the FortiOS management interface to trusted management networks only using firewall policies.

Recommended fix High confidence

FortiOS 7.2.6 or later (for 7.2.x line); FortiOS 7.4.2 or later (for 7.4.x line)

  1. 1. Identify the current FortiOS version by running 'get system status' or checking the FortiOS GUI dashboard.
  2. 2. Determine the appropriate upgrade path based on your current major version (6.4.x, 7.0.x, 7.2.x, or 7.4.x).
  3. 3. Download the fixed FortiOS firmware image (version 7.2.6 or later for 7.2.x line; version 7.4.2 or later for 7.4.x line) from the Fortinet Customer Support portal.
  4. 4. Upload the firmware to the FortiGate device via the GUI (System > Firmware) or CLI using 'execute firmware upload' command.
  5. 5. Back up the current configuration using 'execute backup config' before upgrading.
  6. 6. Initiate the firmware upgrade and allow the device to reboot.
  7. 7. After reboot, verify the upgrade was successful with 'get system status' and confirm the version is >= 7.2.6 or >= 7.4.2.
  8. 8. Validate that the vulnerability is resolved by checking that sensitive information is no longer exposed via HTTP requests.
Caveat Review Fortinet release notes for 7.2.6/7.4.2 for any configuration or feature changes; some features may behave differently after upgrade

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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