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 30 Oct 2024.
FortiproxyApplication · Fortinet

CVE-2024-23113

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to after 7.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 use of externally-controlled format string 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, FortiProxy versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.8, 7.0.0 through 7.0.14, FortiPAM versions 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiSwitchManager versions 7.2.0 through 7.2.3, 7.0.0 through 7.0.3 allows attacker to execute unauthorized code or commands via specially crafted packets.

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

Format string vulnerability in FortiOS, FortiProxy, FortiPAM, and FortiSwitchManager allows remote attackers to execute arbitrary code or commands via specially crafted packets by controlling the format string argument in a vulnerable function.

MitigationUpgrade Fortinet devices to vendor-supplied patched versions: FortiOS 7.4.3+, 7.2.7+, 7.0.14+; FortiProxy 7.4.3+, 7.2.9+, 7.0.15+; FortiPAM 1.3.0+; FortiSwitchManager 7.2.4+, 7.0.4+. If immediate patching is not possible, restrict network access to management interfaces.

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:>= 7.0.0, <= 7.0.14>= 7.2.0, <= 7.2.8>= 7.4.0, <= 7.4.2
FortiswitchmanagerApplication
Affected:>= 7.0.0, <= 7.0.3>= 7.2.0, <= 7.2.3
FortiosOperating system
Affected:>= 7.0.0, <= 7.0.13>= 7.2.0, <= 7.2.6>= 7.4.0, <= 7.4.2
FortipamOperating system
Affected:>= 1.0.0, <= 1.0.3>= 1.1.0, <= 1.1.2= 1.2.0

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 Fortinet product and version
    Access the device CLI or web UI and run the command to display system status (typically 'get system status' in FortiOS/FortiProxy CLI, or check the Dashboard > System Information page in the web UI). Record the product name and firmware version shown.
    Affected if The product is FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager AND the version falls within any of these ranges: FortiOS 7.0.0-7.0.13, 7.2.0-7.2.6, 7.4.0-7.4.2; FortiProxy 7.0.0-7.0.14, 7.2.0-7.2.8, 7.4.0-7.4.2; FortiPAM 1.0.0-1.0.3, 1.1.0-1.1.2, 1.2.0; FortiSwitchManager 7.0.0-7.0.3, 7.2.0-7.2
  2. Verify management interface is exposed
    In the web UI, go to System > Administration Settings or Network > Interfaces. Check which interfaces have HTTP and/or HTTPS management access enabled. In CLI, run 'show system interface' and look for 'set http-server-enable' and 'set allowaccess' entries containing http or https.
    Affected if HTTP or HTTPS management access is enabled on any interface that is reachable from untrusted networks (such as WAN, dialup, or VLANs without firewall policies blocking management traffic).
  3. Confirm if management is reachable from untrusted IPs
    Check the 'Trusted Host' settings under System > Administration Settings or run 'show system admin' to see if admin accounts have restricted trusted host definitions. Also verify interface access lists or firewall policies that may limit management access.
    Affected if The administrative interface (HTTP/HTTPS on any enabled interface) can be reached from IP addresses that are not explicitly defined as trusted hosts, or no trusted host restrictions are configured.

You are affected if you run any of the affected FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager versions AND the management interface is accessible 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 a release after 7.4.2
Interim mitigation

Upgrade Fortinet devices to vendor-supplied patched versions: FortiOS 7.4.3+, 7.2.7+, 7.0.14+; FortiProxy 7.4.3+, 7.2.9+, 7.0.15+; FortiPAM 1.3.0+; FortiSwitchManager 7.2.4+, 7.0.4+. If immediate patching is not possible, restrict network access to management interfaces.

Recommended fix High confidence

FortiOS: 7.0.14+, 7.2.7+, 7.4.3+ | FortiProxy: 7.0.15+, 7.2.9+, 7.4.3+ | FortiPAM: 1.0.4+, 1.1.3+, 1.2.1+ | FortiSwitchManager: 7.0.4+, 7.2.4+

  1. 1. Identify the Fortinet product (FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager) currently deployed in your environment.
  2. 2. Determine the currently installed version by running the appropriate CLI command (e.g., 'get system status' for FortiOS, or checking the GUI dashboard).
  3. 3. For FortiOS: Upgrade to version 7.0.14 or later if on 7.0.x; upgrade to 7.2.7 or later if on 7.2.x; upgrade to 7.4.3 or later if on 7.4.x.
  4. 4. For FortiProxy: Upgrade to version 7.0.15 or later if on 7.0.x; upgrade to 7.2.9 or later if on 7.2.x; upgrade to 7.4.3 or later if on 7.4.x.
  5. 5. For FortiPAM: Upgrade to version 1.0.4 or later if on 1.0.x; upgrade to 1.1.3 or later if on 1.1.x; upgrade to 1.2.1 or later if on 1.2.x.
  6. 6. For FortiSwitchManager: Upgrade to version 7.0.4 or later if on 7.0.x; upgrade to 7.2.4 or later if on 7.2.x.
  7. 7. Download the appropriate firmware from Fortinet's support portal (support.fortinet.com) or the FortiGuard center.
  8. 8. Upload and install the firmware via the device GUI (System > Firmware) or CLI (execute system firmware upgrade).
Caveat Review Fortinet release notes for your specific product and version path to check for potential configuration or feature changes between versions.

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-23113 — 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-23113 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