dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-31496

MEDIUM · 6.7 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 7.2.6 / 7.2.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
A stack-based buffer overflow vulnerability [CWE-121] in Fortinet FortiManager version 7.4.0 through 7.4.2 and before 7.2.5, FortiAnalyzer version 7.4.0 through 7.4.2 and before 7.2.5 and FortiAnalyzer-BigData 7.4.0 and before 7.2.7 allows a 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

A stack-based buffer overflow vulnerability in the CLI interface of FortiManager and FortiAnalyzer allows a privileged attacker to send crafted CLI requests that overflow a stack buffer, potentially enabling arbitrary code or command execution on the affected system.

MitigationUpgrade FortiManager to version 7.4.3 or 7.2.5 or later, FortiAnalyzer to version 7.4.3 or 7.2.5 or later, and FortiAnalyzer-BigData to 7.2.7 or later. Restrict CLI access to trusted, least-privilege administrators only.

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
FortianalyzerApplication
Affected:>= 6.2.0, < 7.2.6>= 7.4.0, < 7.4.3
Fortianalyzer Big DataApplication
Affected:>= 6.2.1, < 7.2.8= 7.4.0
FortimanagerApplication
Affected:>= 6.2.0, < 7.2.6>= 7.4.0, < 7.4.3

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 FortiManager version
    Log into FortiManager web UI, go to System Settings > Dashboard > System Information, or run 'get system status' command in CLI to retrieve the firmware version
    Affected if Version is >= 6.2.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3
  2. Check FortiAnalyzer version
    Log into FortiAnalyzer web UI, go to System Settings > Dashboard > System Information, or run 'get system status' command in CLI to retrieve the firmware version
    Affected if Version is >= 6.2.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3
  3. Check FortiAnalyzer Big Data version
    Log into FortiAnalyzer Big Data web UI, go to System Settings > Dashboard > System Information, or run 'get system status' command in CLI to retrieve the firmware version
    Affected if Version is >= 6.2.1 and < 7.2.8, or = 7.4.0
  4. Verify CLI access is enabled
    In web UI, go to System Settings > Admin > Administrators to check if CLI-based admin accounts exist, or check if port 443 is open for management interface access
    Affected if CLI interface is accessible to privileged users - combined with vulnerable version, the system is exploitable

If the installed FortiManager, FortiAnalyzer, or FortiAnalyzer Big Data version falls within the affected ranges and CLI access is available to privileged users, the system is vulnerable to CVE-2024-31496.

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.6 / 7.2.8 / 7.4.3 or later
Fixed in 7.2.67.2.87.4.3
Interim mitigation

Upgrade FortiManager to version 7.4.3 or 7.2.5 or later, FortiAnalyzer to version 7.4.3 or 7.2.5 or later, and FortiAnalyzer-BigData to 7.2.7 or later. Restrict CLI access to trusted, least-privilege administrators only.

Recommended fix High confidence

FortiManager: 7.2.6+ or 7.4.3+ | FortiAnalyzer: 7.2.6+ or 7.4.3+ | FortiAnalyzer-Big Data: 7.2.8+ or 7.4.1+

  1. Identify the currently installed FortiManager, FortiAnalyzer, or FortiAnalyzer-Big Data version using the CLI command: get system status
  2. For FortiManager: upgrade to version 7.2.6 or later, or version 7.4.3 or later
  3. For FortiAnalyzer: upgrade to version 7.2.6 or later, or version 7.4.3 or later
  4. For FortiAnalyzer-Big Data: upgrade to version 7.2.8 or later, or version 7.4.1 or later
  5. Download the firmware from the Fortinet Customer Support portal: https://support.fortinet.com/
  6. Upload and install the firmware via the FortiManager/FortiAnalyzer GUI under System > Firmware, or via CLI: execute restore image
  7. After upgrade, verify the fix by checking the firmware version: get system status and confirm the version is at or above the fixed release for your product line
Caveat Review Fortinet release notes for your 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 Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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