CVE-2024-23113
Confirmed PUBLISHEDA 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,...
Recommended Action
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
At a Glance
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.
- CVE Published
- Feb 15, 2024
- Exploitation Reported
- Oct 09, 2024
- CVSS
- 9.8 Critical
- EPSS
- —
Affected Versions
42 version rows · page 1 of 2
| Vendor | Product | Version | Status |
|---|---|---|---|
| fortinet |
fortiswitchmanager
|
7.2.0 to <= 7.2.3 |
Affected |
| fortinet |
fortiswitchmanager
|
7.0.0 to <= 7.0.3 |
Affected |
| fortinet |
fortiswitchmanager
|
7.2.0 to <= 7.2.3 |
Affected |
| fortinet |
fortiswitchmanager
|
7.0.0 to <= 7.0.3 |
Affected |
| fortinet |
fortios
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortios
|
7.2.0 to <= 7.2.6 |
Affected |
| fortinet |
fortios
|
7.0.0 to <= 7.0.13 |
Affected |
| fortinet |
fortios
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortios
|
7.2.0 to <= 7.2.6 |
Affected |
| fortinet |
fortios
|
7.0.0 to <= 7.0.13 |
Affected |
| fortinet |
fortios
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortios
|
7.2.0 to <= 7.2.6 |
Affected |
| fortinet |
fortios
|
7.0.0 to <= 7.0.13 |
Affected |
| fortinet |
fortiproxy
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortiproxy
|
7.2.0 to <= 7.2.8 |
Affected |
| fortinet |
fortiproxy
|
7.0.0 to <= 7.0.15 |
Affected |
| fortinet |
fortiproxy
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortiproxy
|
7.2.0 to <= 7.2.8 |
Affected |
| fortinet |
fortiproxy
|
7.0.0 to <= 7.0.15 |
Affected |
| fortinet |
fortiproxy
|
7.4.0 to <= 7.4.2 |
Affected |
| fortinet |
fortiproxy
|
7.2.0 to <= 7.2.8 |
Affected |
| fortinet |
fortiproxy
|
7.0.0 to <= 7.0.15 |
Affected |
| fortinet |
fortipam
|
1.1.0 to <= 1.1.2 |
Affected |
| fortinet |
fortipam
|
1.0.0 to <= 1.0.3 |
Affected |
| fortinet |
fortipam
|
1.2.0 |
Affected |
CVE References
- https://fortiguard.com/psirt/FG-IR-24-029 fortiguard.com · CVE Record https://fortiguard.com/psirt/FG-IR-24-029
Recommended Actions
- Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
- Check enrichment artifacts for scanner coverage and available PoCs before rolling remediation validation.
- Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.
Known Exploited Vulnerability Sources
Catalogues that list this CVE as a known exploited vulnerability.
Per-source evidence links for KEV attestations are available through the KEVIntel Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CISA First | 2024-10-09 00:00 UTC |
No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Virtual Patch
Compensating WAF rules to help reduce exposure to this CVE. Rule content and deployable vendor exports are available with KEVIntel Enterprise.
KEVIntel does not currently have a virtual patch for this CVE. When available, KEVIntel virtual patches ship as deployable ModSecurity, Cloudflare, and AWS WAF rules.
Enterprise feature. Virtual patch rule content and deployable vendor exports (ModSecurity, Cloudflare, AWS WAF) are available to KEVIntel Enterprise users.
CVSS Scores
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:U/RC:C
Exploitation Status
Exploited in the wild
Recorded 2024-10-09 00:00:00 UTC · CISA
Proof of concept available
Recorded 2024-10-21 10:27:52 UTC · GitHub
Weaknesses (CWE)
-
Use of Externally-Controlled Format String
Scanner Integrations
| Scanner | Reference | Detected |
|---|---|---|
| Nessus | https://www.tenable.com/plugins/nessus/190239 | Jun 02, 2025 |
Recent Mentions
Tenable Blog · Apr 25, 2025
Timely vulnerability remediation is an ongoing challenge for organizations as they struggle to prioritize the exposures that represent the greatest risk to their operations. Existing scoring systems are invaluable but can lack context. Here’s how Tenable’s Vulnerability Watch classification system can help.BackgroundOver the past six years working in Tenable’s research organization, I’ve watched known vulnerabilities and zero-day flaws plague organizations in the immediate aftermath of disclosure or even years afterwards. Following each blog post or threat report we’ve published, I kept coming back to the same question: Why are so many organizations struggling to remediate vulnerabilities in a timely manner?As someone who followed the evolution of COVID-19 variants throughout the beginning of the pandemic, I saw that the World Health Organization (WHO) began to label new variants under a classification system as the virus began to mutate. This classification system was designed to help prioritization efforts for monitoring and research. It included accessible labels like variants of interest and variants of concern to help communicate urgency and focus global attention.I began to wonder: What if we borrowed from the same type of classification system used by the WHO and applied it to vulnerability intelligence? Numeric-based systems like the Common Vulnerability Scoring System (CVSS) and Exploit Prediction Scoring System (EPSS) provide mechanisms for prioritization based on scoring. However, they don’t always provide enough context to help decision makers. So, what if we used simple, clear and status-based terminology to communicate risks surrounding vulnerabilities in order to guide action?This led us to develop Vulnerability Watch, a classification system for vulnerabilities inspired by the WHO’s classification of COVID-19 variants. Vulnerability Watch is a small, but important part of Tenable’s Vulnerability Intelligence offering that was launched in 2024. Now,…
Potential Proof of Concepts
These PoCs are unverified and could contain malware. Use at your own risk.
github · Created 2024-10-21 10:27:52 UTC · 6 stars
Timeline
Key exploitation, disclosure, scanner coverage, and KEV attestation events for this CVE.
-
09:26 UTC about 1 year ago09:26 UTC · about 1 year ago
Nessus plugin available
Scanner coverage available
-
10:27 UTC over 1 year ago10:27 UTC · over 1 year ago
Public PoC available
Public proof-of-concept code published
-
00:00 UTC almost 2 years ago00:00 UTC · almost 2 years ago
Added to CISA KEV
Listed in the CISA Known Exploited Vulnerabilities catalog
-
13:59 UTC over 2 years ago13:59 UTC · over 2 years ago
CVE published
Vulnerability disclosed publicly
-
16:29 UTC over 2 years ago16:29 UTC · over 2 years ago
CVE ID reserved
Identifier reserved by the CNA
Automate This Intelligence with the Pro API
Confidence scoring, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
Pro API Example
GET /api/v2/pro/kevs/CVE-2024-23113
{
"cve_id": "CVE-2024-23113",
"title": "A use of externally-controlled format string in Fortinet FortiOS versions 7.4...",
"affected_vendor": "Fortinet",
"affected_product": "FortiSwitchManager, FortiOS, FortiPAM, FortiProxy",
"affected_versions": [
{ "vendor": "...", "product": "...", "status": "affected", "display_label": "..." }
],
"confidence": "Confirmed",
"cvss_score": 9.8,
"epss_score": null,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "...": "Pro API fields" },
"proof_of_concepts": [ "..." ],
"scanner_integrations": [ "..." ]
}