dbcve.org
FortimailApplication · Fortinet

CVE-2024-56497

MEDIUM · 6.7 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 6.4.5 / 6.4.8 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') in Fortinet FortiMail versions 7.2.0 through 7.2.4 and 7.0.0 through 7.0.6 and 6.4.0 through 6.4.7, FortiRecorder versions 7.0.0 and 6.4.0 through 6.4.4 allows attacker to execute unauthorized code or commands via the CLI.

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 FortiMail and FortiRecorder CLI allows authenticated attackers to execute arbitrary OS commands by injecting special elements into CLI parameters. Affected versions span FortiMail 7.2.0-7.2.4, 7.0.0-7.0.6, 6.4.0-6.4.7 and FortiRecorder 7.0.0, 6.4.0-6.4.4.

MitigationApply Fortinet patches: FortiMail 7.2.5/7.0.7/6.4.8 and FortiRecorder 7.0.1/6.4.5 or later. Until patched, limit CLI access to trusted administrators only and monitor for suspicious command execution.

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
FortimailApplication
Affected:>= 6.4.0, < 6.4.8>= 7.0.0, < 7.0.7>= 7.2.0, < 7.2.5
FortirecorderApplication
Affected:>= 6.4.0, < 6.4.5>= 7.0.0, < 7.0.2

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 the installed Fortinet product
    Determine whether FortiMail or FortiRecorder is deployed in your environment. Check the product name via the web UI, CLI, or system documentation.
    Affected if The product is FortiMail or FortiRecorder and is accessible via CLI.
  2. Determine the installed version of FortiMail
    Log into the FortiMail CLI and run the command to display the firmware version, typically 'get system status' or check the web UI dashboard for the firmware version.
    Affected if The displayed version falls within 6.4.0 through 6.4.7, 7.0.0 through 7.0.6, or 7.2.0 through 7.2.4.
  3. Determine the installed version of FortiRecorder
    Log into the FortiRecorder CLI and run the command to display the firmware version, typically 'get system status' or check the web UI dashboard for the firmware version.
    Affected if The displayed version falls within 6.4.0 through 6.4.4 or 7.0.0.
  4. Verify CLI access exists for your account
    Confirm you have CLI access credentials and can authenticate to the FortiMail or FortiRecorder CLI interface.
    Affected if You can log into the CLI with an authenticated account, as the vulnerability requires an authenticated attacker.

You are affected if you have FortiMail version 6.4.0-6.4.7, 7.0.0-7.0.6, or 7.2.0-7.2.4, OR FortiRecorder version 6.4.0-6.4.4 or 7.0.0, and the CLI interface is accessible to your user account.

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.5 / 6.4.8 / 7.0.2 or later
Fixed in 6.4.56.4.87.0.2
Interim mitigation

Apply Fortinet patches: FortiMail 7.2.5/7.0.7/6.4.8 and FortiRecorder 7.0.1/6.4.5 or later. Until patched, limit CLI access to trusted administrators only and monitor for suspicious command execution.

Recommended fix High confidence

FortiMail: 6.4.8, 7.0.7, or 7.2.5 (depending on current branch); FortiRecorder: 6.4.5 or 7.0.2

  1. 1. Identify the currently installed FortiMail and/or FortiRecorder version via CLI (get system status) or web UI.
  2. 2. Determine which upgrade path applies based on your current major.minor version branch.
  3. 3. Backup the current configuration - for FortiMail use 'execute backup config tftp/ftp/sftp <remote>' or web UI backup; for FortiRecorder use equivalent backup command.
  4. 4. Download the appropriate fixed firmware from Fortinet support portal: FortiMail 6.4.8, 7.0.7, or 7.2.5; FortiRecorder 6.4.5 or 7.0.2.
  5. 5. Upload and install the firmware via web UI (System > Firmware) or CLI ('execute firmware upgrade').
  6. 6. After reboot, verify the version upgrade was successful with 'get system status'.
  7. 7. Confirm normal operation and test critical email processing/recording functions.
Caveat Standard firmware upgrade risks apply - review release notes for minor behavioral changes; backup before upgrading

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

Fix this in Fortimail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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