# CVE-2012-1570: Business logic in n/a

> Remote attackers can manipulate DNS cache to keep revoked domains resolvable, affecting MaraDNS server administrators.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-1570, GHSA-v2q2-mfxj-3q9c

## What is CVE-2012-1570?

CVE-2012-1570 is a medium-severity vulnerability in n/a, published on 28 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The resolver in MaraDNS before 1.3.0.7.15 and 1.4.x before 1.4.12 overwrites cached server names and TTL values in NS records during the processing of a response to an A record query, which allows remote attackers to trigger continued resolvability of revoked domain names via a "ghost domain names" attack.

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

It affects 1 product.


Products: Maradns Maradns.

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

Upgrade to a fixed version.

## Is CVE-2012-1570 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0024](https://insights.sbomify.com/CVE-2012-0024/): Denial of service in n/a (high 7.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1570 is a medium-severity vulnerability in n/a, published on 28 Mar 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-1570 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-1570/ (Markdown: https://insights.sbomify.com/CVE-2012-1570/index.md)
```

## Sources

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

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