dbcve.org
FortisiemApplication · Fortinet

CVE-2023-34992

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 6.7.5 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
A 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 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

This is an OS command injection vulnerability in Fortinet products where crafted API requests are not properly sanitized, allowing attackers to inject and execute arbitrary OS commands on the affected system. The vulnerability stems from improper neutralization of special elements in API input that gets passed to system shell commands.

MitigationImplement strict input validation and parameterized queries or avoid shell command execution entirely. Sanitize all API inputs to remove or escape shell metacharacters before passing to system calls.

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.6.0, <= 6.6.3>= 6.7.0, <= 6.7.5= 6.4.0= 6.4.1= 6.4.2= 6.5.0= 6.5.1= 7.0.0

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 version
    Run 'phstatus -v' or check the Fortisiem web UI under Admin > System Management > System Information to find the installed version number
    Affected if The installed version matches any of these: 6.4.0, 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.7.0-6.7.5, 6.6.0-6.6.3, or 7.0.0
  2. Verify API access is enabled
    Check Fortisiem UI under Admin > Settings > API Settings or review httpd.conf to determine if the REST API service is enabled and accessible
    Affected if API access is enabled on the Fortisiem appliance, exposing the injection vector
  3. Review API access logs
    Examine Fortisiem event logs or system logs for API endpoint calls, particularly look in /var/log/phoenix or the API access logs for unusual or unexpected API requests
    Affected if There are API requests containing shell metacharacters like ; | & $ ` or $( ) that were processed by the system
  4. Check for unauthorized command execution
    Review bash history, audit logs, or process execution logs on the Fortisiem server for unexpected commands or scripts that did not originate from legitimate administrative actions
    Affected if Commands appear in logs that were not initiated by known administrators or legitimate Fortisiem processes

You are affected if Fortisiem is running any of the vulnerable versions listed and the API service is exposed and accessible to potential attackers.

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 6.7.5
Interim mitigation

Implement strict input validation and parameterized queries or avoid shell command execution entirely. Sanitize all API inputs to remove or escape shell metacharacters before passing to system calls.

Recommended fix Moderate confidence

FortiSIEM 6.7.6 or later (for 6.7.x users); FortiSIEM 6.6.4 or later (for 6.6.x users); FortiSIEM 6.4.2 or later (for 6.4.x users)

  1. Identify your current FortiSIEM version using the web UI (System > Administration > License > Version) or CLI: 'phvtadmin --version'
  2. Review FortiSIEM release notes on fortiguard.com for version 6.7.6 or later, and 6.6.4 or later
  3. Upgrade to the latest stable FortiSIEM release (recommended: 6.7.6 or later for 6.7.x line; 6.6.4 or later for 6.6.x line)
  4. After upgrade, verify the version is no longer in the affected list: not 6.6.0-6.6.3, 6.7.0-6.7.5, or 6.4.0-6.4.1
  5. Restrict API access to authorized admin IPs using FortiSIEM GUI: Define IP restrictions under System > Administration > Settings > Access Control
  6. Enable audit logging for all API calls under System > Settings > Logging > Audit Log
Caveat Upgrading FortiSIEM may require downtime and could affect existing configurations; review migration guides and backup current configuration before proceeding

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

Fix this in Fortisiem Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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 locally
dbcve dependency scanner

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