FortianalyzerApplication · Fortinet

CVE-2024-32123

MEDIUM · 6.7 CVSS v3.1 Published 2025-03-11

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

NVD · unedited

Multiple improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiManager, FortiAnalyzer versions 7.4.0 through 7.4.2 7.2.0 through 7.2.5 and 7.0.0 through 7.0.12 and 6.4.0 through 6.4.14 and 6.2.0 through 6.2.12 and 6.0.0 through 6.0.12 and 5.6.0 through 5.6.11 and 5.4.0 through 5.4.7 and 5.2.0 through 5.2.10 and 5.0.0 through 5.0.12 and 4.3.4 through 4.3.8 allows attacker to execute unauthorized code or commands via crafted CLI requests.

Technical summary

dbcve analysis · moderate confidence

OS command injection vulnerability in FortiManager and FortiAnalyzer CLI interface allows attackers to execute unauthorized operating system commands via specially crafted CLI requests. The vulnerability affects numerous versions across multiple major releases (7.x, 6.x, 5.x, 4.x), indicating a systemic input validation failure in CLI parameter handling.

MitigationApply Fortinet patches to upgrade to versions 7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+, 6.2.13+, 6.0.13+, 5.6.12+, 5.4.8+, 5.2.11+, 5.0.13+, or 4.3.9+ as appropriate. Restrict CLI access to authorized administrative 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

NVD · CPE data

FortianalyzerApplication

Affected:>= 6.2.0, < 7.2.6>= 7.4.0, < 7.4.4

Fortianalyzer Big DataApplication

Affected:>= 6.4.5, < 7.2.8>= 7.4.0, < 7.4.2

FortimanagerApplication

Affected:>= 4.3.4, < 7.2.6>= 7.4.0, < 7.4.4

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check FortiManager version via CLI

Log into the FortiManager CLI and run: `get system status` or `execute get system version`. Look for the Firmware/Version field.

Affected if The version displayed is >= 4.3.4 and < 7.2.6, OR >= 7.4.0 and < 7.4.4
Check FortiAnalyzer version via CLI

Log into the FortiAnalyzer CLI and run: `get system status` or `execute get system version`. Look for the Firmware/Version field.

Affected if The version displayed is >= 6.2.0 and < 7.2.6, OR >= 7.4.0 and < 7.4.4
Check FortiAnalyzer Big Data version via CLI

Log into the FortiAnalyzer Big Data CLI and run: `get system status` or `execute get system version`. Look for the Firmware/Version field.

Affected if The version displayed is >= 6.4.5 and < 7.2.8, OR >= 7.4.0 and < 7.4.2
Check version via Web UI

Access the web UI, navigate to System > Settings or Dashboard > System Information. Locate the Firmware version displayed.

Affected if The version shown matches the affected ranges in steps 1-3 above
Verify CLI access exposure

Review network accessibility of the CLI interface (port 23/telnet or port 22/SSH). Check admin profiles and trusted hosts configured under `config system admin`.

Affected if CLI is reachable from untrusted networks or admin accounts have overly broad access rights

If the installed FortiManager, FortiAnalyzer, or FortiAnalyzer Big Data firmware version falls within any of the listed affected ranges, the system is vulnerable to OS command injection via the CLI interface.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 7.2.6 / 7.2.8 / 7.4.2 or later

Fixed in 7.2.67.2.87.4.2

Interim mitigation

Apply Fortinet patches to upgrade to versions 7.4.3+, 7.2.6+, 7.0.13+, 6.4.15+, 6.2.13+, 6.0.13+, 5.6.12+, 5.4.8+, 5.2.11+, 5.0.13+, or 4.3.9+ as appropriate. Restrict CLI access to authorized administrative personnel and monitor for suspicious CLI activity.

Recommended fix High confidence

FortiManager: upgrade to 7.2.6+ or 7.4.4+ | FortiAnalyzer: upgrade to 7.2.6+ or 7.4.4+ | FortiAnalyzer Big Data: upgrade to 7.2.8+ or 7.4.2+

1. Identify the currently installed Fortinet product (FortiManager, FortiAnalyzer, or FortiAnalyzer Big Data) and its exact version using the CLI command 'get system status' or through the web UI.
2. Determine the appropriate upgrade path based on your current major version branch.
3. For FortiManager: upgrade to version 7.2.6 or later, or 7.4.4 or later.
4. For FortiAnalyzer: upgrade to version 7.2.6 or later, or 7.4.4 or later.
5. For FortiAnalyzer Big Data: upgrade to version 7.2.8 or later, or 7.4.2 or later.
6. Before upgrading, backup the current configuration using 'execute backup config' or through the web UI.
7. Download the firmware from the Fortinet Customer Support portal (https://support.fortinet.com/).
8. Upload and install the firmware through the web UI (System > Firmware) or via CLI using 'execute firmware upgrade'.

Caveat Major firmware upgrades may require reconfiguration; review release notes for migration considerations and ensure compatibility with managed devices before upgrading.

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

Fix this in Fortianalyzer Scoped from the published advisory

Consultation8.0 h
Implementation4.0 h
Testing6.0 h
Review / QA4.0 h

22.0 hours of engineering $3,940

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

fortiguard.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32123 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-32123?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 7.2.6 / 7.2.8 or later

Severity 6.7 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Fortianalyzer

Remediation

Need this fixed?

Fix this in Fortianalyzer 22 hrs · Moderate

Typical engagement from $3,940

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-32123 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References