dbcve.org
FortivoiceApplication · Fortinet

CVE-2024-40587

MEDIUM · 6.7 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 6.4.10 / 7.0.5 or later.
See remediation →
69/100
Remediation priority · Elevated
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 [CWE-78] in Fortinet FortiVoice version 7.0.0 through 7.0.4 and before 6.4.9 allows an authenticated privileged attacker to execute unauthorized code or commands via crafted CLI 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 (CWE-78) in Fortinet FortiVoice phone systems. An authenticated privileged attacker can execute arbitrary OS commands by sending specially crafted CLI requests. The vulnerability affects versions 7.0.0 through 7.0.4 and versions before 6.4.9.

MitigationUpgrade FortiVoice to version 7.0.5 or later, or 6.4.9 or later. Until patched, limit CLI access to only highly trusted, essential personnel and monitor for suspicious CLI activity.

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
FortivoiceApplication
Affected:>= 6.0.0, < 6.4.10>= 7.0.0, < 7.0.5

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 FortiVoice installation
    Locate FortiVoice by checking running processes, listening services on typical management ports (443, 80, 22), or the FortiVoice web interface at the system's management URL.
    Affected if FortiVoice software is found running on the system.
  2. Determine installed FortiVoice version
    Access the FortiVoice CLI or web interface and run the command to display the system version, typically 'get system status' via CLI or check the About/Dashboard section in the web GUI.
    Affected if The displayed version falls within the ranges 6.0.0 to 6.4.9, or 7.0.0 to 7.0.4.
  3. Verify CLI access is enabled
    Confirm that the command-line interface (CLI) service is accessible, typically via SSH on port 22 or through the FortiVoice console. Check if CLI access is permitted in the system configuration.
    Affected if CLI access is enabled and reachable on the network.
  4. Review CLI access controls
    Examine the user accounts with CLI privileges and verify which users have administrative or elevated access rights that could exploit this vulnerability.
    Affected if Multiple users or untrusted accounts have administrative CLI privileges.
  5. Inspect for suspicious CLI activity
    Review CLI command logs or audit trails for unexpected or unauthorized commands, particularly those involving shell execution, file operations, or system configuration changes.
    Affected if Unknown or malicious CLI commands appear in logs.

A system is affected if FortiVoice version 6.0.0 through 6.4.9 or 7.0.0 through 7.0.4 is installed and CLI access is available to untrusted or compromised privileged users.

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 6.4.10 / 7.0.5 or later
Fixed in 6.4.107.0.5
Interim mitigation

Upgrade FortiVoice to version 7.0.5 or later, or 6.4.9 or later. Until patched, limit CLI access to only highly trusted, essential personnel and monitor for suspicious CLI activity.

Recommended fix High confidence

FortiVoice 6.4.10 or later (6.x branch); FortiVoice 7.0.5 or later (7.x branch)

  1. 1. Identify the current FortiVoice version by accessing the system via CLI or web UI
  2. 2. Determine which branch (6.x or 7.x) is currently in use
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up the current FortiVoice configuration via web UI (System > Maintenance > Backup & Restore) or CLI
  5. 5. Download the appropriate firmware from Fortinet Customer Support (https://support.fortinet.com/) for the target fixed version: 6.4.10 or later for 6.x branch, 7.0.5 or later for 7.x branch
  6. 6. Upload the firmware file via FortiVoice web UI (System > Maintenance > Firmware) or CLI
  7. 7. Follow the on-screen prompts to install the firmware upgrade
  8. 8. After reboot, verify the system is operational and the new version is installed
Caveat Review Fortinet release notes for the target version to check for any configuration or feature changes that may require adjustment

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

Fix this in Fortivoice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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