llamaCVEVulnerability Intelligence
/
Advisory · GitHub · crates.io · hickory-proto

GHSA-V7PC-74H8-XQ2H

Hickory DNS failure to verify self-signed RRSIG for DNSKEYs

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -3 d de la divulgación
Exposición647 dDesde la divulgación, 10 feb 2025, 4:52 p. m.
Detección644 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 0.24.3 +1
Monitoreo
Detectada
7 feb 25
10 feb 25
10 sept 26
17 nov 26
19 nov 26
7 feb 25
20 jul 25
29 dic 25
10 jun 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 0.24.3 hickory-proto · -3 d desde divulgación
Remediación Parche 0.25.0-alpha.5 hickory-proto · -3 d desde divulgación
Divulgación Publicada GHSA-V7PC-74H8-XQ2H divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

The DNSSEC validation routines treat entire RRsets of DNSKEY records as trusted once they have established trust in only one of the DNSKEYs. As a result, if a zone includes a DNSKEY with a public key that matches a configured trust anchor, all keys in that zone will be trusted to authenticate other records in the zone. There is a second variant of this vulnerability involving DS records, where an authenticated DS record covering one DNSKEY leads to trust in signatures made by an unrelated DNSKEY in the same zone.

Details

verify_dnskey_rrset() will return Ok(true) if any record's public key matches a trust anchor. This results in verify_rrset() returning a Secure proof. This ultimately results in successfully verifying a response containing DNSKEY records. verify_default_rrset() looks up DNSKEY records by calling handle.lookup(), which takes the above code path. There's a comment following this that says "DNSKEYs were already validated by the inner query in the above lookup", but this is not the case. To fully verify the whole RRset of DNSKEYs, it would be necessary to check self-signatures by the trusted key over the other keys. Later in verify_default_rrset(), verify_rrset_with_dnskey() is called multiple times with different keys and signatures, and if any call succeeds, then its Proof is returned.

Similarly, verify_dnskey_rrset() returns Ok(false) if any DNSKEY record is covered by a DS record. A comment says "If all the keys are valid, then we are secure", but this is only checking that one key is authenticated by a DS in the parent zone's delegation point. This time, after control flow returns to verify_rrset(), it will call verify_default_rrset(). The special handling for DNSKEYs in verify_default_rrset() will then call verify_rrset_with_dnskey() using each KSK DNSKEY record, and if one call succeeds, return its Proof. If there are multiple KSK DNSKEYs in the RRset, then this leads to another authentication break. We need to either pass the authenticated DNSKEYs from the DS covering check to the RRSIG validation, or we need to perform this RRSIG validation of the DNSKEY RRset inside verify_dnskey_rrset() and cut verify_default_rrset() out of DNSKEY RRset validation entirely.

Versiones

Rangos afectados

Afectada Corregida Última
hickory-proto≥ 0.8.0 < 0.24.3
hickory-proto≥ 0.25.0-alpha.1 < 0.25.0-alpha.5
0.8.0
0.24.3
0.25.0-alpha.1
0.25.0-alpha.5
0.26.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
crates.iohickory-proto
Corregida 0.24.3, 0.25.0-alpha.5 -3 d · -3 d 0.26.3 no afectada
Versiones corregidas0.24.30.25.0-alpha.5
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-37wc-h8xc-5hc4
Otrahttps://github.com/hickory-dns/hickory-dns
Otrahttps://rustsec.org/advisories/RUSTSEC-2025-0006.html

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.