# CVE-2007-2362: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via buffer overflows in MyDNS update handling.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1434-1, DTSA-36-1, GHSA-8c5w-487x-q6x4

## What is CVE-2007-2362?

CVE-2007-2362 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in MyDNS 1.1.0 allow remote attackers to (1) cause a denial of service (daemon crash) and possibly execute arbitrary code via a certain update, which triggers a heap-based buffer overflow in update.c; and (2) cause a denial of service (daemon crash) via unspecified vectors that trigger an off-by-one stack-based buffer overflow in update.c.

## Which versions are affected by CVE-2007-2362?

It affects 1 product.


Products: Don Moore Mydns.

## How do I fix CVE-2007-2362?

Apply the vendor's patch.

## Is CVE-2007-2362 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2362 exists.

Public exploit code:

- MyDNS 1.1.0 - Remote Heap Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-2075](https://insights.sbomify.com/CVE-2006-2075/): Denial of service in n/a (medium 5.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-2007-2362 and fix it if it is affected.

What it is: CVE-2007-2362 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2362 exists.

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-2007-2362/ (Markdown: https://insights.sbomify.com/CVE-2007-2362/index.md)
```

## Sources

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

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