Skip to content

DNSSEC validation accepts bogus positive response with wildcard expansion

Low
divergentdave published GHSA-vrv5-968r-5ggm Sep 3, 2026

Package

cargo hickory-net (Rust)

Affected versions

0.26.0-beta.1 .. 0.26.1

Patched versions

0.26.2
cargo hickory-proto (Rust)
<= 0.26.0-alpha.1
None

Description

DNSSEC validation does not sufficiently distinguish between NODATA respones and positive responses with wildcard expansion. If a query is made that should result in a NODATA response, and the zone has records with wildcard names, it is possible for an attacker to combine an NSEC3 record matching the query name, the record with a wildcard name, and its signature into a bogus positive response that will be accepted by DNSSEC validation. If the query name is proven to exist, then wildcard expansion should not be performed, and an answer section with a wildcard-expanded positive response should not be accepted.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

Improperly Implemented Security Check for Standard

The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. Learn more on MITRE.

Credits