# CVE-2006-0527: BIND 4 (BIND4) and BIND 8 (BIND8), if used as a target forwarder, allows remote attackers to gain privileged access via a "Kashpureff-style


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q2rh-q7xj-6gw7

## What is CVE-2006-0527?

CVE-2006-0527 is a high-severity vulnerability in Isc Bind, published on 2 Feb 2006. 

### Official description

BIND 4 (BIND4) and BIND 8 (BIND8), if used as a target forwarder, allows remote attackers to gain privileged access via a "Kashpureff-style DNS cache corruption" attack.

Weakness: CWE-264

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

It affects 1 product.


Products: Isc Bind.

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

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

## Is CVE-2006-0527 being exploited?

There is no known exploitation of CVE-2006-0527 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-2006-0527 and fix it if it is affected.

What it is: CVE-2006-0527 is a high-severity vulnerability in Isc Bind, published on 2 Feb 2006. 
Exploitation: There is no known exploitation of CVE-2006-0527 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-2006-0527/ (Markdown: https://insights.sbomify.com/CVE-2006-0527/index.md)
```

## Sources

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

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