# CVE-2024-45289: Unbounded allocation in ctl(4) CAM Target Layer

> Incorrect environment variable handling in the fetch library causes the revocation file option to be ignored, allowing connections to hosts with revoked certificates.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-34p7-67p6-m2pf

## What is CVE-2024-45289?

CVE-2024-45289 is a high-severity vulnerability in FreeBSD, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The fetch(3) library uses environment variables for passing certain information, including the revocation file pathname.  The environment variable name used by fetch(1) to pass the filename to the library was incorrect, in effect ignoring the option.

Fetch would still connect to a host presenting a certificate included in the revocation file passed to the --crl option.

Weakness: CWE-665 (Improper Initialization)

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


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

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

## Is CVE-2024-45289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45289 is a high-severity vulnerability in FreeBSD, published on 12 Nov 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-45289 in the wild and no public exploit code.

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

## Sources

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

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