BIND DNSSEC NSEC/NSEC3 validation code could cause bogus NXDOMAIN responses
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | |||
| bind-30:9.3.6-4.P1.el5_4.2 | cpe:/o:redhat:enterprise_linux:5 | RHSA-2010:0062 | 2010-01-20T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-2054-1 | New bind9 packages fix cache poisoning |
Debian DSA |
DSA-2054-2 | New bind9 packages fix cache poisoning |
EUVD |
EUVD-2010-0129 | ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain. |
Ubuntu USN |
USN-888-1 | Bind vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 9.4% (9.363% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.