Hickory DNS before 0.26.0-beta.1 DNSSEC Validation Bypass via Non-IN Class Records
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hickory-dns | hickory-dns | unaffected |
|
|||||||||
| hickory-dns | hickory-dns | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hickory-dns | Hickory-dns |
|
||||||||||||
| Hickory-dns | Hickory-dns |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.120% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hickory-dns
Hickory-dns hickory-dns |
|
| Vendors & Products |
Hickory-dns
Hickory-dns hickory-dns |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hickory DNS hickory-proto before 0.26.0-beta.1 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because verify_rrsets() ignores DNS class when partitioning RRsets, so non-IN records skip signature verification yet are marked secure when the IN records verify. Attackers able to supply DNS responses can include forged CH or HS class records, including DS records, to authenticate any DNSKEY and forge child zone responses. | |
| Title | Hickory DNS before 0.26.0-beta.1 DNSSEC Validation Bypass via Non-IN Class Records | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV3_1
|