# CVE-2010-3615: Missing authorization in n/a

> Remote attackers can bypass access controls to read private DNS records due to improper ACL checks in ISC BIND.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 3 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-3615, GHSA-j2v8-rqc3-xfr2

## What is CVE-2010-3615?

CVE-2010-3615 is a medium-severity missing authorization vulnerability in Isc Bind, published on 3 Dec 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

named in ISC BIND 9.7.2-P2 does not check all intended locations for allow-query ACLs, which might allow remote attackers to make successful requests for private DNS records via the standard DNS query mechanism.

Weakness: CWE-264

## Which versions are affected by CVE-2010-3615?

It affects 1 product.


Products: Isc Bind.

## How do I fix CVE-2010-3615?

Upgrade to a fixed version.

## Is CVE-2010-3615 being exploited?

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

What it is: CVE-2010-3615 is a medium-severity missing authorization vulnerability in Isc Bind, published on 3 Dec 2010. 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-2010-3615 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-2010-3615/ (Markdown: https://insights.sbomify.com/CVE-2010-3615/index.md)
```

## Sources

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

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