dbcve.org
FortindrApplication · Fortinet

CVE-2024-47573

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 7.2.2 / 7.4.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 validation of integrity check value vulnerability [CWE-354] in FortiNDR version 7.4.2 and below, version 7.2.1 and below, version 7.1.1 and below, version 7.0.6 and below may allow an authenticated attacker with at least Read/Write permission on system maintenance to install a corrupted firmware image.

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

FortiNDR fails to properly validate the integrity check value of firmware images before installation, allowing an authenticated attacker with Read/Write permissions on system maintenance to install a corrupted firmware image. This is a CWE-354 (Improper Validation of Integrity Check Value) vulnerability affecting multiple version branches up to 7.4.2.

MitigationApply vendor-supplied patches for FortiNDR to address the firmware integrity validation flaw. Ensure only trusted administrators with necessary permissions can access system maintenance functions.

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
FortindrApplication
Affected:>= 7.0.0, < 7.2.2>= 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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 FortiNDR firmware version
    Access the FortiNDR CLI and run the command 'get system status' or 'diagnose system full-stat' to retrieve the current firmware version installed on the device
    Affected if The displayed version falls within 7.0.0 to 7.2.1, or 7.4.0 to 7.4.2 (for example, 7.0.5, 7.2.0, 7.4.1)
  2. Confirm version via web UI
    Log into the FortiNDR web interface, navigate to the Dashboard or System settings section, and locate the firmware version information typically displayed in the device status or about page
    Affected if The version shown matches the affected ranges above

You are affected if your FortiNDR version is 7.0.0 through 7.2.1, or 7.4.0 through 7.4.2; versions 7.2.2 and above (including 7.4.3 and later) are not vulnerable.

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.2 / 7.4.3 or later
Fixed in 7.2.27.4.3
Interim mitigation

Apply vendor-supplied patches for FortiNDR to address the firmware integrity validation flaw. Ensure only trusted administrators with necessary permissions can access system maintenance functions.

Recommended fix High confidence

FortiNDR 7.2.2 or 7.4.3 (depending on current branch)

  1. 1. Identify the current FortiNDR version by navigating to System > Firmware or using 'get system status' CLI command
  2. 2. Determine which upgrade path applies: if running 7.0.x, upgrade to 7.2.2 first (then to 7.4.3 if needed); if running 7.2.x, upgrade to 7.2.2; if running 7.4.0-7.4.2, upgrade to 7.4.3
  3. 3. Download the firmware image from Fortinet Customer Support portal (https://support.fortinet.com) for the target version
  4. 4. Back up the current FortiNDR configuration via System > Maintenance > Backup & Restore
  5. 5. Navigate to System > Firmware and upload the new firmware image
  6. 6. Verify the upgrade was successful by confirming the new version in System > Firmware or via 'get system status' command
  7. 7. Confirm the integrity check validation is now functioning correctly by reviewing release notes for the fixed version
Caveat Review release notes for the target version to confirm compatibility with existing Fortinet ecosystem components and any configuration changes required

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

Fix this in Fortindr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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