# CVE-2008-3337: Other in n/a

> Remote attackers can poison DNS caches by sending malformed queries to PowerDNS Authoritative Server, impacting data integrity for other systems.

- **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:** 8 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3337, DSA-1628-1, GHSA-rj9p-mrcp-3f7h

## What is CVE-2008-3337?

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

### Official description

PowerDNS Authoritative Server before 2.9.21.1 drops malformed queries, which might make it easier for remote attackers to poison DNS caches of other products running on other servers, a different issue than CVE-2008-1447 and CVE-2008-3217.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Powerdns Authoritative Server, Powerdns Powerdns.

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

Upgrade to a fixed version.

## Is CVE-2008-3337 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36754](https://insights.sbomify.com/CVE-2021-36754/): Denial of service in n/a (high 7.5)
- [CVE-2012-0206](https://insights.sbomify.com/CVE-2012-0206/): Denial of service in n/a (medium 5.0)
- [CVE-2019-10203](https://insights.sbomify.com/CVE-2019-10203/): Integer overflow in pdns (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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