# CVE-2012-0024: Denial of service in n/a

> Remote attackers can cause CPU exhaustion and denial of service in MaraDNS by sending crafted queries that trigger predictable hash collisions.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 8 Jan 2012
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-0024, GHSA-34xr-8rpc-3j54

## What is CVE-2012-0024?

CVE-2012-0024 is a high-severity denial of service vulnerability in n/a, published on 8 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MaraDNS before 1.3.07.12 and 1.4.x before 1.4.08 computes hash values for DNS data without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted queries with the Recursion Desired (RD) bit set.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2012-0024?

It affects 1 product.


Products: Maradns Maradns.

## How do I fix CVE-2012-0024?

Upgrade to a fixed version.

## Is CVE-2012-0024 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3115](https://insights.sbomify.com/CVE-2007-3115/): Denial of service in n/a (high 7.8)
- [CVE-2022-30256](https://insights.sbomify.com/CVE-2022-30256/): Other in n/a (high 7.5)
- [CVE-2011-0520](https://insights.sbomify.com/CVE-2011-0520/): Memory corruption in n/a (high 7.5)
- [CVE-2011-5055](https://insights.sbomify.com/CVE-2011-5055/): Denial of service in n/a (medium 5.0)
- [CVE-2008-0061](https://insights.sbomify.com/CVE-2008-0061/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0024 and fix it if it is affected.

What it is: CVE-2012-0024 is a high-severity denial of service vulnerability in n/a, published on 8 Jan 2012. 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-2012-0024 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-2012-0024/ (Markdown: https://insights.sbomify.com/CVE-2012-0024/index.md)
```

## Sources

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

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