dbcve.org
FortisiemApplication · Fortinet

CVE-2024-23109

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 7.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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 improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet allows attacker to execute unauthorized code or commands via via crafted API 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

OS command injection vulnerability in Fortinet products allowing remote attackers to execute arbitrary operating system commands via crafted API requests. The vulnerability results from improper neutralization of special elements in user-supplied input being passed to system shell commands.

MitigationApply the vendor-provided Fortinet security patch (FG-IR-24-029) to all affected Fortinet devices. Immediately restrict API access to trusted sources and implement network segmentation to limit exposure until patches can be deployed.

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
FortisiemApplication
Affected:>= 6.4.0, <= 6.4.2>= 6.5.0, <= 6.5.2>= 6.6.0, <= 6.6.3>= 6.7.0, <= 6.7.8>= 7.0.0, <= 7.0.2= 7.1.0= 7.1.1

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 Fortisiem installation
    Locate Fortisiem software on the system. Check for Fortisiem directories, services, or web interfaces typically accessible on ports 443 or 8080.
    Affected if Fortisiem software is found on the system
  2. Determine Fortisiem version
    Access the Fortisiem web UI or CLI and retrieve the installed version number. In the web interface, navigate to Admin > System Settings > General or use the 'phCon' CLI tool with version command.
    Affected if The installed version falls within any of these ranges: 6.4.0-6.4.2, 6.5.0-6.5.2, 6.6.0-6.6.3, 6.7.0-6.7.8, 7.0.0-7.0.2, 7.1.0, or 7.1.1
  3. Verify API endpoint accessibility
    Check if the Fortisiem API endpoints are exposed to network access. Identify whether the web interface/API is accessible from untrusted networks by reviewing firewall rules, reverse proxy configurations, or network ACLs.
    Affected if API endpoints are reachable from untrusted or external networks without proper access restrictions
  4. Confirm authentication configuration
    Review Fortisiem authentication settings for API access. Check whether API key-based authentication or user authentication is required and properly enforced for API requests.
    Affected if API access is available without requiring valid authentication or uses weak/default credentials
  5. Check for command injection exposure
    Since the vulnerability involves crafted API requests being passed to system shell commands, verify whether API request logging shows suspicious input patterns or if the web server process runs with elevated privileges.
    Affected if The system accepts API requests that could contain shell metacharacters and processes them through system shell commands

A system is affected if Fortisiem is installed and the version matches one of the listed vulnerable ranges AND the API interface is network-accessible, allowing unauthenticated or weakly-authenticated command injection through crafted requests.

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.0.2
Interim mitigation

Apply the vendor-provided Fortinet security patch (FG-IR-24-029) to all affected Fortinet devices. Immediately restrict API access to trusted sources and implement network segmentation to limit exposure until patches can be deployed.

Recommended fix Moderate confidence

Upgrade to the latest available Fortisiem release: 6.7.9 or later (or the latest 6.4.3/6.5.3/6.6.4 for your respective branch)

  1. Identify your current Fortisiem version from the affected list: 6.4.x, 6.5.x, 6.6.x, or 6.7.x
  2. For Fortisiem 6.4.x: upgrade to version 6.4.3 or later
  3. For Fortisiem 6.5.x: upgrade to version 6.5.3 or later
  4. For Fortisiem 6.6.x: upgrade to version 6.6.4 or later
  5. For Fortisiem 6.7.x: upgrade to version 6.7.9 or later
  6. After upgrade, verify the Fortisiem GUI shows the new version under System > Health > Diagnostics
  7. Review FortiGuard PSIRT advisory FG-IR-24-029 for full release notes
Caveat Review Fortinet release notes for your target version; standard minor upgrades typically do not introduce breaking changes but test in staging first

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

Fix this in Fortisiem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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