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

> Remote attackers can cause a denial of service in PowerDNS by sending malformed DNS packets, requiring an upgrade to fix.

- **Severity:** Medium 5.0 (`AV:N/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:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0428, GHSA-crv6-r2rx-hphg

## What is CVE-2005-0428?

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

### Official description

The DNSPacket::expand method in dnspacket.cc in PowerDNS before 2.9.17 allows remote attackers to cause a denial of service by sending a random stream of bytes.

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

It affects 1 product.


Products: Powerdns Powerdns.

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

Upgrade to a fixed version.

## Is CVE-2005-0428 being exploited?

There is no known exploitation of CVE-2005-0428 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-2008-5277](https://insights.sbomify.com/CVE-2008-5277/): Denial of service in n/a (medium 4.3)
- [CVE-2005-2302](https://insights.sbomify.com/CVE-2005-2302/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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