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

> Remote attackers can crash the DNS server or leak memory by sending crafted resource records with zero-length data.

- **Severity:** High 8.5 (`AV:N/AC:L/Au:N/C:P/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:** 5 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-1667, DSA-2486-1, GHSA-8wqw-72q7-h4q9, RHSA-2012:1110

## What is CVE-2012-1667?

CVE-2012-1667 is a high-severity denial of service vulnerability in Isc Bind, published on 5 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ISC BIND 9.x before 9.7.6-P1, 9.8.x before 9.8.3-P1, 9.9.x before 9.9.1-P1, and 9.4-ESV and 9.6-ESV before 9.6-ESV-R7-P1 does not properly handle resource records with a zero-length RDATA section, which allows remote DNS servers to cause a denial of service (daemon crash or data corruption) or obtain sensitive information from process memory via a crafted record.

Weakness: CWE-189

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bind` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind-chroot` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind-debuginfo` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind-devel` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind-libs` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind-utils` | Red Hat:rhel_els:4::as | All versions | 20:9.2.4-39.el4 |
| `bind` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |
| `bind-chroot` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |
| `bind-debuginfo` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |
| `bind-devel` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |
| `bind-libs` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |
| `bind-utils` | Red Hat:rhel_els:4::es | All versions | 20:9.2.4-39.el4 |

Products: Isc Bind.

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

Upgrade to a fixed version.

## Is CVE-2012-1667 being exploited?

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

## Other vulnerabilities in Isc Bind

- [CVE-2008-0122](https://insights.sbomify.com/CVE-2008-0122/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0010](https://insights.sbomify.com/CVE-2001-0010/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0011](https://insights.sbomify.com/CVE-2001-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0013](https://insights.sbomify.com/CVE-2001-0013/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1029](https://insights.sbomify.com/CVE-2000-1029/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1667 is a high-severity denial of service vulnerability in Isc Bind, published on 5 Jun 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-1667 in the wild and no public exploit code.

Affected product: Isc Bind. 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-1667/ (Markdown: https://insights.sbomify.com/CVE-2012-1667/index.md)
```

## Sources

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

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