# CVE-2004-0789: Denial of service in n/a

> Remote attackers can cause denial of service in DNS implementations by triggering communication loops via spoofed packets.

- **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:** No
- **Published:** 1 Sep 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3jm2-9cp5-5xp7

## What is CVE-2004-0789?

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

### Official description

Multiple implementations of the DNS protocol, including (1) Poslib 1.0.2-1 and earlier as used by Posadis, (2) Axis Network products before firmware 3.13, and (3) Men & Mice Suite 2.2x before 2.2.3 and 3.5.x before 3.5.2, allow remote attackers to cause a denial of service (CPU and network bandwidth consumption) by triggering a communications loop via (a) DNS query packets with localhost as a spoofed source address, or (b) a response packet that triggers a response packet.

## Which versions are affected by CVE-2004-0789?

It affects 15 products.


Products: Axis 2100 Network Camera, Axis 2110 Network Camera, Axis 2120 Network Camera, Axis 2400 Video Server, Axis 2401 Video Server, Axis 2420 Network Camera, Axis 2460 Network Dvr, Delegate Delegate, Dnrd Dnrd, Don Moore Mydns, Maradns Maradns, Pliant Pliant Dns Server, Posadis Posadis, Qbik Wingate, Team Johnlong Raidendnsd.

## How do I fix CVE-2004-0789?

No fix has been published for CVE-2004-0789 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-0789 being exploited?

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

Public exploit code:

- https://github.com/HimmeL-Byte/CVE-2004-0789-DDOS (github_poc): https://github.com/HimmeL-Byte/CVE-2004-0789-DDOS

## Other vulnerabilities in n/a

- [CVE-2004-2427](https://insights.sbomify.com/CVE-2004-2427/): Missing authorization in n/a (critical 10.0)
- [CVE-2003-0240](https://insights.sbomify.com/CVE-2003-0240/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-5213](https://insights.sbomify.com/CVE-2007-5213/): Cross-site request forgery in n/a (critical 9.3)
- [CVE-2007-2239](https://insights.sbomify.com/CVE-2007-2239/): Memory corruption in n/a (critical 9.3)
- [CVE-2004-2425](https://insights.sbomify.com/CVE-2004-2425/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0789 and fix it if it is affected.

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

## Sources

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

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