# CVE-2007-2926: Weak cryptography in n/a

> Weak random number generation in ISC BIND allows remote attackers to guess DNS query IDs and perform cache poisoning.

- **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:** 24 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2926, DSA-1341-2, GHSA-f6h8-pjrf-562j, RHSA-2007:0740

## What is CVE-2007-2926?

CVE-2007-2926 is a medium-severity vulnerability in Isc Bind, published on 24 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ISC BIND 9 through 9.5.0a5 uses a weak random number generator during generation of DNS query ids when answering resolver questions or sending NOTIFY messages to slave name servers, which makes it easier for remote attackers to guess the next query id and perform DNS cache poisoning.

## Which versions are affected by CVE-2007-2926?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bind` | Red Hat:enterprise_linux:2.1::as | All versions | 0:9.2.1-9.el2 |
| `bind-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 0:9.2.1-9.el2 |
| `bind-utils` | Red Hat:enterprise_linux:2.1::as | All versions | 0:9.2.1-9.el2 |
| `bind` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:9.2.1-9.el2 |
| `bind-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:9.2.1-9.el2 |
| `bind-utils` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:9.2.1-9.el2 |
| `bind` | Red Hat:enterprise_linux:2.1::es | All versions | 0:9.2.1-9.el2 |
| `bind-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 0:9.2.1-9.el2 |
| `bind-utils` | Red Hat:enterprise_linux:2.1::es | All versions | 0:9.2.1-9.el2 |
| `bind` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:9.2.1-9.el2 |
| `bind-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:9.2.1-9.el2 |
| `bind-utils` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:9.2.1-9.el2 |
| `bind` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind-chroot` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind-devel` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind-libs` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind-utils` | Red Hat:enterprise_linux:3::as | All versions | 20:9.2.4-21.el3 |
| `bind` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind-chroot` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind-libs` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind-utils` | Red Hat:enterprise_linux:3::desktop | All versions | 20:9.2.4-21.el3 |
| `bind` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind-chroot` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind-devel` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind-libs` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind-utils` | Red Hat:enterprise_linux:3::es | All versions | 20:9.2.4-21.el3 |
| `bind` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind-chroot` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind-devel` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind-libs` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind-utils` | Red Hat:enterprise_linux:3::ws | All versions | 20:9.2.4-21.el3 |
| `bind` | Red Hat:enterprise_linux:4::as | All versions | 20:9.2.4-27.0.1.el4 |
| `bind-chroot` | Red Hat:enterprise_linux:4::as | All versions | 20:9.2.4-27.0.1.el4 |
| `bind-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 20:9.2.4-27.0.1.el4 |
| `bind-devel` | Red Hat:enterprise_linux:4::as | All versions | 20:9.2.4-27.0.1.el4 |

Products: Isc Bind.

## How do I fix CVE-2007-2926?

Upgrade to a fixed version.

## Is CVE-2007-2926 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2926 exists.

Public exploit code:

- BIND 9 0.3beta - DNS Cache Poisoning (exploitdb)

## 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-2007-2926 and fix it if it is affected.

What it is: CVE-2007-2926 is a medium-severity vulnerability in Isc Bind, published on 24 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2926 exists.

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-2007-2926/ (Markdown: https://insights.sbomify.com/CVE-2007-2926/index.md)
```

## Sources

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

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