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

GHSA-4JWP-XJWM-333G

Missing IPv4-Mapped IPv6 address canonicalization

Sin parche publicado
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición77 dDesde la divulgación, 3 sept 2026, 4:54 p. m.
Detección76 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 0.26.2
Monitoreo
Detectada +1
3 sept 26
18 nov 26
19 nov 26
3 sept 26
23 sept 26
12 oct 26
31 oct 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-4JWP-XJWM-333G divulgada
Remediación Parche 0.26.2 hickory-resolver · 0 d desde divulgación
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

When checking IP addresses against a resolver's answer address filter, a recursor's do not query filters, or a server's client allow list, IPv4-Mapped-IPv6 addresses were not canonicalized. For the resolver use-case, this could result in addresses not being properly filtered from the response message. For the recursor use case, this could result in connections being made to nameservers that should have been denied. For the server use-case, this could have allowed clients to access the server that should have been denied (if library code was providing IPv6 listen sockets that did not specify `set_only_v6(true)` - the `hickory-dns` binary is not affected).

Users of `hickory-proto` 0.26.0 .. 0.26.1 built with the non-default `access-control` feature that relied on the `AccessControlSet` are affected. Users of `hickory-resolver` 0.26.0 .. 0.26.1 configured using `ResolverOpts` that set `deny_answers` are affected. Similarly users of `hickory-resolver` 0.26.0 .. 0.26.1 with the non-default `recursor` feature that set `RecursorOptions` with `deny_answers` or `deny_server` are affected. Users of the (now-defunct) `hickory-recursor` crate 0.25.0-alpha.3 ... 0.26.0-alpha.1 that set `RecursorOptions` with `deny_answers` or `deny_server` are affected. Lastly, library users of `hickory-server` 0.25.0-alpha.1 ... 0.26.1 that use `Server::with_access()` are affected if `register_socket()` is also used with IPv6 sockets that do not specify `set_only_v6(true)`.

Reporter:

Qifan Zhang, Palo Alto Networks

Versiones

Rangos afectados

Afectada Corregida Última
hickory-recursortodas
hickory-resolver · hickory-proto · hickory-server< 0.26.2
0.25.2
0.26.2
0.26.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
crates.iohickory-recursor
Sin parche — — 0.25.2 afectada
crates.iohickory-resolver
Corregida 0.26.2 0 d 0.26.3 no afectada
crates.iohickory-proto
Corregida 0.26.2 0 d 0.26.3 no afectada
crates.iohickory-server
Corregida 0.26.2 0 d 0.26.3 no afectada
Versiones corregidas0.26.2
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-4jwp-xjwm-333g

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