# CVE-2009-0858: Other in n/a

> Remote attackers can inject arbitrary DNS records into responses by exploiting improper offset constraints in djbdns when controlling a third-party subdomain.

- **Severity:** Medium 5.8 (`AV:N/AC:M/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:** 9 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0858, DSA-1831-1, GHSA-f296-f6r3-pgjg

## What is CVE-2009-0858?

CVE-2009-0858 is a medium-severity vulnerability in n/a, published on 9 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The response_addname function in response.c in Daniel J. Bernstein djbdns 1.05 and earlier does not constrain offsets in the required manner, which allows remote attackers, with control over a third-party subdomain served by tinydns and axfrdns, to trigger DNS responses containing arbitrary records via crafted zone data for this subdomain.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: D.j.bernstein Djbdns.

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

Apply the vendor's patch.

## Is CVE-2009-0858 being exploited?

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

Public exploit code:

- djbdns 1.05 - Long Response Packet Remote Cache Poisoning (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-1191](https://insights.sbomify.com/CVE-2012-1191/): Other in n/a (medium 6.4)
- [CVE-2008-4392](https://insights.sbomify.com/CVE-2008-4392/): Race condition in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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