# CVE-2024-47573: Security feature bypass in FortiNDR

> Authenticated attackers with maintenance permissions can bypass integrity checks to install corrupted firmware, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H/E:U/RL:X/RC:X`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2025
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-v2mv-99jp-98vc

## What is CVE-2024-47573?

CVE-2024-47573 is a medium-severity vulnerability in Fortinet FortiNDR, published on 14 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2024-47573?

It affects 1 product.


Products: Fortinet Fortindr.

## How do I fix CVE-2024-47573?

No fix has been published for CVE-2024-47573 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-47573 being exploited?

There is no known exploitation of CVE-2024-47573 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet FortiNDR

- [CVE-2023-48790](https://insights.sbomify.com/CVE-2023-48790/): Cross-site request forgery in FortiNDR (high 7.1)
- [CVE-2024-23104](https://insights.sbomify.com/CVE-2024-23104/): Information disclosure in FortiNDR (medium 5.4)
- [CVE-2026-25088](https://insights.sbomify.com/CVE-2026-25088/): SQL injection in FortiNDR (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47573 and fix it if it is affected.

What it is: CVE-2024-47573 is a medium-severity vulnerability in Fortinet FortiNDR, published on 14 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47573 in the wild and no public exploit code.

Affected product: Fortinet FortiNDR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47573/ (Markdown: https://insights.sbomify.com/CVE-2024-47573/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47573
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47573
- OSV: https://osv.dev/vulnerability/CVE-2024-47573

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47573/
Summaries are generated and may contain mistakes; the official description above is the record.