# CVE-2006-2075: Denial of service in n/a

> Remote attackers can cause a denial of service in MyDNS by sending a crafted DNS message, affecting DNS server availability.

- **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:** 27 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vm5h-7v78-mjjr

## What is CVE-2006-2075?

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

### Official description

Unspecified vulnerability in MyDNS 1.1.0 allows remote attackers to cause a denial of service via a crafted DNS message, aka "Query-of-death," as demonstrated by the OUSPG PROTOS DNS test suite.

## Which versions are affected by CVE-2006-2075?

It affects 1 product.


Products: Don Moore Mydns.

## How do I fix CVE-2006-2075?

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

## Is CVE-2006-2075 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2362](https://insights.sbomify.com/CVE-2007-2362/): Memory corruption in n/a (critical 9.0)
- [CVE-2006-0351](https://insights.sbomify.com/CVE-2006-0351/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2075 and fix it if it is affected.

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

## Sources

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

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