Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| NLnet Labs | Unbound | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nlnetlabs | Unbound |
|
Vendor Solution
This issue is fixed starting with version 1.26.2
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-6581-1 | unbound security update |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.111% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nlnetlabs
Nlnetlabs unbound |
|
| Vendors & Products |
Nlnetlabs
Nlnetlabs unbound |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an additional 'trust-anchor:' for an island-of-security zone whose parent is provably insecure under the root chain, a malicious actor with a forged NSEC reply with the SOA bit cleared can trick Unbound to treat the configured trust island as insecure. This happens because the DNSSEC validator in Unbound accepts and caches the NSEC insecure response bypassing the RRSIG validation that the validator was supposed to do. The acceptance of the NSEC record at the trust anchor apex was allowed due to and old fix for type DS and NSEC queries from clients when trust anchor for that name existed. | |
| Title | Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record. | |
| Weaknesses | CWE-354 | |
| References |
| |
| Metrics |
cvssV3_1
|