# CVE-2024-45237: Memory corruption in n/a

> A buffer overflow in the Fort library allows attackers to execute code or cause denial of service via malicious RPKI certificates.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Aug 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-45237, GHSA-wpp2-87q7-h53v, UBUNTU-CVE-2024-45237

## What is CVE-2024-45237?

CVE-2024-45237 is a critical memory corruption vulnerability in n/a, published on 24 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Fort before 1.6.3. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) a resource certificate containing a Key Usage extension composed of more than two bytes of data. Fort writes this string into a 2-byte buffer without properly sanitizing its length, leading to a buffer overflow.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Nicmx Fort-Validator.

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

Upgrade to a fixed version.

## Is CVE-2024-45237 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-45234](https://insights.sbomify.com/CVE-2024-45234/): Denial of service in n/a (high 7.5)
- [CVE-2024-45236](https://insights.sbomify.com/CVE-2024-45236/): Denial of service in n/a (high 7.5)
- [CVE-2024-45239](https://insights.sbomify.com/CVE-2024-45239/): Null dereference in n/a (high 7.5)
- [CVE-2024-56170](https://insights.sbomify.com/CVE-2024-56170/): Other in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45237 is a critical memory corruption vulnerability in n/a, published on 24 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45237 in the wild and no public exploit code.

Affected product: n/a. 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-45237/ (Markdown: https://insights.sbomify.com/CVE-2024-45237/index.md)
```

## Sources

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

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