GHSA-JR2J-7HVH-H4Q9
Incomplete SSRF denylist coverage for IPv6 transition ranges
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-JR2J-7HVH-H4Q9 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Incomplete SSRF denylist coverage for IPv6 transition ranges
Summary
Nezha uses a restricted HTTP client for user-configurable notification and DDNS webhook URLs. In versions 2.0.10 through 2.3.2, its denylist did not explicitly cover the 6to4 prefix `2002::/16`. These addresses pass Go `netip.Addr.IsGlobalUnicast`, so the URL validator accepted them.
Maintainer assessment of the 6to4 report
Thank you to tonghuaroot for identifying the missing range. We confirmed that the validator accepted `2002::/16` addresses and have blocked the range as defense in depth.
We did not confirm the originally described direct cloud-metadata path. 6to4 is IPv6-over-IPv4 encapsulation, not IPv6-to-IPv4 translation. A request to `2002:a9fe:a9fe::1` remains an IPv6 TCP request carried inside IPv4 protocol 41; it does not become an IPv4 HTTP request to `169.254.169.254`. RFC 3056 also requires 6to4 routers to discard destinations embedding non-global IPv4 addresses. Reaching loopback, RFC 1918, or cloud metadata endpoints would therefore require additional non-standard or misconfigured transition infrastructure and a reachable IPv6 endpoint.
Because exploitation is highly environment-dependent and the direct metadata path is not valid for standards-compliant 6to4, this advisory is rated Low.
Affected versions
- Affected: `>= 2.0.10, < 2.3.3`
- Patched: `2.3.3`
Impact
An authenticated user who can configure a webhook may be able to reach an otherwise restricted IPv6 endpoint only when the dashboard network provides unusual or non-compliant routing for the affected transition range. No direct conversion to an IPv4 metadata, loopback, or private-network HTTP request has been demonstrated.
Patches
Version 2.3.3 blocks both:
- `2002::/16`, the 6to4 transition prefix.
- `64:ff9b:1::/48`, the local-use IPv4/IPv6 translation prefix identified during the follow-up audit.
Regression tests cover direct IP validation and literal URL resolution while confirming ordinary public IPv4 and IPv6 targets remain allowed.
Fixed in commit: https://github.com/nezhahq/nezha/commit/d1fcde8e
Release: https://github.com/nezhahq/nezha/releases/tag/v2.3.3
Workarounds
Upgrade to 2.3.3 or later. Operators unable to upgrade should restrict untrusted users from configuring notification or DDNS webhook URLs and enforce outbound network policy for the dashboard process.
References
- RFC 3056: https://www.rfc-editor.org/rfc/rfc3056
- RFC 3964: https://www.rfc-editor.org/rfc/rfc3964
Credit
Reported by tonghuaroot.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/nezhahq/nezha |
Sin parche | — | — | v1.14.14 no afectada |
2.3.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/nezhahq/nezha/security/advisories/GHSA-jr2j-7hvh-h4q9Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
