dbcve.org
FortimailApplication · Fortinet

CVE-2024-46663

MEDIUM · 6.7 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 7.2.7 / 7.4.4 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
A stack-buffer overflow vulnerability [CWE-121] in Fortinet FortiMail CLI version 7.6.0 through 7.6.1 and before 7.4.3 allows a privileged attacker to execute arbitrary code or commands via specifically crafted CLI commands.

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 confidence

A stack-buffer overflow vulnerability (CWE-121) exists in FortiMail CLI versions 7.6.0 through 7.6.1 and before 7.4.3. An authenticated privileged attacker can send specially crafted CLI commands to overflow a stack-based buffer, potentially achieving arbitrary code or command execution on the affected FortiMail appliance.

MitigationApply the appropriate Fortinet patch to upgrade FortiMail to version 7.4.3 or later, or the latest 7.6.x release that includes the fix. Limit CLI access to only necessary privileged administrators and monitor for anomalous CLI command patterns.

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, < 7.2.7>= 7.4.0, < 7.4.4>= 7.6.0, < 7.6.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. Check FortiMail firmware version
    Log into the CLI and run: execute sysinfo or get system status. Alternatively, access the web UI and check Dashboard > Status to view the firmware version.
    Affected if The installed version is 6.4.0 through 7.2.6, or 7.4.0 through 7.4.3, or 7.6.0 through 7.6.1 (i.e., it falls within any of the vulnerable ranges)
  2. Confirm CLI access is enabled
    From the web UI, go to System > Access Profile > CLI Settings, or run: get system admin. Verify whether CLI access is granted to any administrator accounts.
    Affected if CLI access is enabled for privileged administrators, providing the attack surface for this vulnerability
  3. Identify administrator accounts with privileged access
    Run: get system admin. Review the list of administrators and their profile assignments to identify those with full or elevated privileges.
    Affected if Multiple or unnecessary privileged administrator accounts exist, increasing the risk of exploitation

You are affected if your FortiMail runs a version within 6.4.0 to <7.2.7, 7.4.0 to <7.4.4, or 7.6.0 to <7.6.2 and has CLI access enabled for 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 7.2.7 / 7.4.4 / 7.6.2 or later
Fixed in 7.2.77.4.47.6.2
Interim mitigation

Apply the appropriate Fortinet patch to upgrade FortiMail to version 7.4.3 or later, or the latest 7.6.x release that includes the fix. Limit CLI access to only necessary privileged administrators and monitor for anomalous CLI command patterns.

Recommended fix High confidence

FortiMail 7.2.7, 7.4.4, or 7.6.2 depending on current version branch

  1. Identify the currently installed FortiMail version by running: get system status or via the web UI under Dashboard > Status
  2. Determine which version branch your current installation belongs to (6.4.x, 7.2.x, 7.4.x, or 7.6.x)
  3. For FortiMail 6.4.x: upgrade to FortiMail 7.2.7 or later recommended
  4. For FortiMail 7.2.x (< 7.2.7): upgrade to FortiMail 7.2.7
  5. For FortiMail 7.4.x (< 7.4.4): upgrade to FortiMail 7.4.4
  6. For FortiMail 7.6.x (< 7.6.2): upgrade to FortiMail 7.6.2
  7. Download the firmware from Fortinet Customer Support portal or FortiGuard
  8. Back up FortiMail configuration before upgrade
Caveat Review FortiMail release notes for any configuration or feature changes between versions; minor point upgrades typically have minimal breaking changes

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

Fix this in Fortimail Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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