GHSA-2VGH-3WFW-QJ7C
RRSIG Signer's Name not checked against the RRset's zone
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-2VGH-3WFW-QJ7C divulgada | |
| Remediación | Parche 0.26.2 | hickory-net · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Previously the Hickory DNS validator authenticated an RRset by fetching the DNSKEY RRset for whatever name appears in the RRSIG Signer's Name field and verifying the signature against that key, but never checked that the signer name is the zone that contains the RRset (as required by RFC 4035 §5.3.1 https://www.rfc-editor.org/rfc/rfc4035#section-5.3.1, second bullet). An attacker who controls any secure zone in the public DNS can therefore produce a cryptographically-valid RRSIG over arbitrary records at an arbitrary name in an unrelated zone.
The bug is reachable by any caller of `DnssecDnsHandle`, including the resolver, recursor, and client, when built with the `dnssec-ring` or `dnssec-aws-lc-rs` feature and configured to perform DNSSEC validation.
The affected code was migrated from `hickory-proto` to `hickory-net` as part of the 0.26.0 release, meaning `hickory-proto` versions 0.1 .. 0.25.0-alpha.3 are affected, while `hickory-proto` v0.25.0-alpha.4+ is not affected. Conversely all versions of `hickory-net` are affected until the patched version.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
crates.iohickory-proto |
Sin parche | — | — | 0.26.3 afectada |
crates.iohickory-net |
Corregida | 0.26.2 | 0 d | 0.26.3 no afectada |
0.26.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-2vgh-3wfw-qj7cLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
