# CVE-2024-12107: Double Free in µD3TN

> A remote attacker can cause a denial of service in the µD3TN library by sending a malformed endpoint identifier, triggering a double-free error.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-xp4h-q65r-x2pm, PYSEC-2024-300

## What is CVE-2024-12107?

CVE-2024-12107 is a high-severity use after free vulnerability in µD3TN, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double-Free Vulnerability in uD3TN BPv7 Caused by Malformed Endpoint Identifier allows remote attacker to reliably cause DoS

Weakness: CWE-415 (Double Free)

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

1 open source package ship an affected version, including pyd3tn. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyd3tn` | PyPI | All versions to 0.13.0 | None |

Products: D3tn Ud3tn.

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

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

## Is CVE-2024-12107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12107 exists.

## Other vulnerabilities in µD3TN

- [CVE-2025-8183](https://insights.sbomify.com/CVE-2025-8183/): NULL Pointer Dereference in µD3TN (high 7.5)
- [CVE-2024-10455](https://insights.sbomify.com/CVE-2024-10455/): Reachable Assertion in µD3TN (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12107 is a high-severity use after free vulnerability in µD3TN, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12107 exists.

Affected packages and fixed versions:
- pyd3tn (PyPI): affected all versions up to 0.13.0; no fix listed

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

## Sources

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

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