# CVE-2008-2469: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a crafted DNS TXT record due to a heap-based buffer overflow in the libspf2 library.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2469, DSA-1659-1, DTSA-172-1, GHSA-jc7w-hj86-2rr5

## What is CVE-2008-2469?

CVE-2008-2469 is a critical memory corruption vulnerability in n/a, published on 23 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the SPF_dns_resolv_lookup function in Spf_dns_resolv.c in libspf2 before 1.2.8 allows remote attackers to execute arbitrary code via a long DNS TXT record with a modified length field.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-2469?

It affects 1 product.


Products: Libspf Libspf2.

## How do I fix CVE-2008-2469?

Upgrade to a fixed version.

## Is CVE-2008-2469 being exploited?

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

Public exploit code:

- LibSPF2 < 1.2.8 - DNS TXT Record Parsing Bug Heap Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2469 and fix it if it is affected.

What it is: CVE-2008-2469 is a critical memory corruption vulnerability in n/a, published on 23 Oct 2008. 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-2008-2469 exists.

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

## Sources

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

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