Skip to content
vulnerability

CVE-2024-23113

9.8
Critical
KEV · Exploited in wildEPSS 62%Patch available

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.

exploited
Yes, in CISA KEV since 9 Oct 2024fix by 30 Oct 2024 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 61.7%
Published 15 Feb 2024Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: noAV · networkCWE-134· Common Weakness

Can a WAF block it? No. The vulnerability is triggered by specially crafted packets sent to the affected Fortinet products, which use non-HTTP protocols. Such packets do not have a distinct pattern that a web application firewall could reliably detect without blocking legitimate traffic.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2024-23113 being exploited?

Yes. CVE-2024-23113 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-23113?

CVE-2024-23113 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-23113?

Yes. A fix has been recorded for CVE-2024-23113. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-23113 affect?

CVE-2024-23113 affects fortinet:fortiproxy, fortinet:fortiswitchmanager, fortinet:fortios, fortinet:fortipam. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
fortinet:fortiproxyfortinet:fortiswitchmanagerfortinet:fortiosfortinet:fortipam
affected versions
Fortinet FortiOS
  • affected>= 7.4.0 and <= 7.4.2
  • affected>= 7.2.0 and <= 7.2.6
  • affected>= 7.0.0 and <= 7.0.13
Fortinet FortiPAM
  • affected1.2.0
  • affected>= 1.1.0 and <= 1.1.2
  • affected>= 1.0.0 and <= 1.0.3
Fortinet FortiProxy
  • affected>= 7.4.0 and <= 7.4.2
  • affected>= 7.2.0 and <= 7.2.8
  • affected>= 7.0.0 and <= 7.0.15
Fortinet FortiSwitchManager
  • affected>= 7.2.0 and <= 7.2.3
  • affected>= 7.0.0 and <= 7.0.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept

GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 9 Oct 2024 (SSVC 2.0.3).

timeline

  1. 15 Feb 2024Published
  2. 9 Oct 2024Added to CISA KEV (exploited in the wild) · 236 days (about 8 months) later
  3. 9 Oct 2024CISA SSVC assessment: exploitation active · 1 day later
  4. 11 Oct 2024First proof-of-concept repository on GitHub (unvetted) · 1 day later
  5. 30 Oct 2024CISA remediation due date (US federal agencies) · 19 days later
  6. 21 Oct 2025CVE record last updated · 357 days (about 12 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 2 links
  • Linkfortiguard.com /psirt/FG-IR-24-029
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-23113

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved