Skip to content

CVE-2024-23113

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…

Critical Known exploited
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
61.72%
Chance of exploitation in the next 30 days. Higher than 99.17% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Oct 9, 2024
Weakness
CWE-134 Use of Externally-Controlled Format String
Fix
None yet
No fixed version published
Exploited in the wild. Fortinet Multiple Products Format String Vulnerability (Fortinet Multiple Products). Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Oct 30, 2024.

Description

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.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 9.8

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-134: Use of Externally-Controlled Format String

The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

How to prevent it
  • Requirements: Choose a language that is not subject to this flaw.
  • Implementation: Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings. [REF-116] [REF-117]
  • Build and Compilation: Run compilers and linkers with high warning levels, since they may detect incorrect usage.

References

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-3m6g-2423-7cp3
Ruby JSON has a format string injection vulnerability
Critical Same weakness, CWE-134
GHSA-w96v-gf22-crwp
n8n: Webhook Node IP Whitelist Bypass via Partial String Matching
Medium Same weakness, CWE-134
GHSA-9ccg-6pjw-x645
ImageMagick has a Format String Bug in InterpretImageFilename leads to arbitrary code execution
High Same weakness, CWE-134
GHSA-q3gg-m8hr-h4x4
Externally Controlled Format String in Scripting Functions
Critical Same weakness, CWE-134
GHSA-5rp4-749p-vx26
Apache Airflow vulnerable to Use of Externally-Controlled Format String
High Same weakness, CWE-134
CVE-2021-25489
Assuming radio permission is gained, missing input validation in modem interface driver prior to SMR Oct-2021 Release 1 results in format string bug leading to…
Medium Known exploited Same weakness, CWE-134
GHSA-qvm7-23cj-437v
Remote Code Execution in Apache Dubbo
Critical Same weakness, CWE-134
GHSA-xmq7-7fxm-rr79
Denial of Service in Tensorflow
High Same weakness, CWE-134
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor