# CVE-2005-2302: Denial of service in n/a

> An attacker can cause a denial of service by triggering a blanking of DNS answers for authorized clients when recursion is restricted.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/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:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2302, GHSA-6w24-r92j-wj7q

## What is CVE-2005-2302?

CVE-2005-2302 is a low-severity denial of service vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PowerDNS before 2.9.18, when allowing recursion to a restricted range of IP addresses, does not properly handle questions from clients that are denied recursion, which could cause a "blank out" of answers to those clients that are allowed to use recursion.

## Which versions are affected by CVE-2005-2302?

It affects 1 product.


Products: Powerdns Powerdns.

## How do I fix CVE-2005-2302?

Upgrade to a fixed version.

## Is CVE-2005-2302 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0038](https://insights.sbomify.com/CVE-2005-0038/): Denial of service in n/a (medium 5.0)
- [CVE-2006-2069](https://insights.sbomify.com/CVE-2006-2069/): Denial of service in n/a (medium 5.0)
- [CVE-2005-2301](https://insights.sbomify.com/CVE-2005-2301/): Other in n/a (medium 5.0)
- [CVE-2005-0428](https://insights.sbomify.com/CVE-2005-0428/): Denial of service in n/a (medium 5.0)
- [CVE-2008-5277](https://insights.sbomify.com/CVE-2008-5277/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2302 and fix it if it is affected.

What it is: CVE-2005-2302 is a low-severity denial of service vulnerability in n/a, published on 19 Jul 2005. 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-2005-2302 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-2005-2302/ (Markdown: https://insights.sbomify.com/CVE-2005-2302/index.md)
```

## Sources

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

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