# CVE-2008-4099: Security feature bypass in n/a

> Remote attackers can spoof DNS responses because the library uses predictable source ports and transaction IDs, bypassing DNS security mechanisms.

- **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:** 18 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9547-8gx6-787g

## What is CVE-2008-4099?

CVE-2008-4099 is a medium-severity vulnerability in n/a, published on 18 Sep 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PyDNS (aka python-dns) before 2.3.1-4 in Debian GNU/Linux does not use random source ports or transaction IDs for DNS requests, which makes it easier for remote attackers to spoof DNS responses, a different vulnerability than CVE-2008-1447.

Weakness: CWE-16

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

It affects 1 product.


Products: Debian Python-Dns.

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

Upgrade to a fixed version.

## Is CVE-2008-4099 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4126](https://insights.sbomify.com/CVE-2008-4126/): Security feature bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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