HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-22870US | — | Exploit | ||
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com"… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2025/03/07/2WEB
- https://go-review.googlesource.com/q/project:netPACKAGE
- https://go.dev/cl/654697WEB
- https://go.dev/issue/71984WEB
- https://groups.google.com/g/golang-announce/c/4t3lzH3I0eI/m/b42ImqrBAQAJWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-22870ADVISORY
- https://pkg.go.dev/vuln/GO-2025-3503WEB
- https://security.netapp.com/advisory/ntap-20250509-0007WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan