# CVE-2009-1086: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a malformed DNS resource record in the ldns library.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1086, DSA-1795-1, GHSA-5957-cmgf-chq8

## What is CVE-2009-1086?

CVE-2009-1086 is a medium-severity memory corruption vulnerability in n/a, published on 25 Mar 2009. 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 ldns_rr_new_frm_str_internal function in ldns 1.4.x allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code via a DNS resource record (RR) with a long (1) class field (clas variable) and possibly (2) TTL field.

Weakness: CWE-399

## Which versions are affected by CVE-2009-1086?

It affects 1 product.


Products: Nlnetlabs Ldns.

## How do I fix CVE-2009-1086?

Upgrade to a fixed version.

## Is CVE-2009-1086 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000231](https://insights.sbomify.com/CVE-2017-1000231/): Use after free in n/a (critical 9.8)
- [CVE-2017-1000232](https://insights.sbomify.com/CVE-2017-1000232/): Use after free in n/a (critical 9.8)
- [CVE-2026-10846](https://insights.sbomify.com/CVE-2026-10846/): Insufficient verification that responses belong to a query (high 8.2)
- [CVE-2020-19861](https://insights.sbomify.com/CVE-2020-19861/): Information disclosure in n/a (high 7.5)
- [CVE-2011-3581](https://insights.sbomify.com/CVE-2011-3581/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1086 and fix it if it is affected.

What it is: CVE-2009-1086 is a medium-severity memory corruption vulnerability in n/a, published on 25 Mar 2009. 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-2009-1086 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-2009-1086/ (Markdown: https://insights.sbomify.com/CVE-2009-1086/index.md)
```

## Sources

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

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