FortisiemApplication · Fortinet
CVE-2024-23108
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 · uneditedAn 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 · moderate confidenceCVE-2024-23108 is a critical OS command injection vulnerability in Fortinet products that allows attackers to execute unauthorized system commands through specially crafted API requests. The vulnerability stems from improper neutralization of special elements in user-supplied input that gets passed to underlying OS command execution functions.
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
>= 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.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Fortisiem is installedIdentify if Fortinet Fortisiem is present in your environment by checking the product name through system inventory, running processes, or the application's web interface/CLI.Affected if Fortisiem product is found in the environment
-
Check Fortisiem versionDetermine the installed Fortisiem version by accessing the web UI (typically under System > Settings or About), or using the CLI command 'phver' or 'fortisiem-software-version' if available.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
-
Verify API access is enabledCheck if the Fortisiem API interface is enabled and accessible by reviewing the API service configuration in the web UI under API Settings or by examining network listening services on the appliance.Affected if The API service is enabled and exposed to network traffic
-
Review logs for suspicious command executionExamine Fortisiem logs (typically in /var/log/ or accessible via the UI under Log Explorer) for unusual or unauthorized system commands, especially those originating from API requests, looking for unexpected command strings or shell executions.Affected if Logs show unfamiliar commands or API-request-initiated shell executions that were not initiated by legitimate administrators
You are affected if Fortisiem is installed, the version matches one of the vulnerable ranges listed, and the API interface is accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied Fortinet patch immediately; until then, restrict API access to trusted IPs only and monitor for suspicious command execution patterns in logs.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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