Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA 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 | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hickory-dns | hickory-dns | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hickory-dns | Hickory-dns |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.118% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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 | The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation. | |
| Title | Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV3_1
|