HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net
Go standard library net/http · golang.org/x/net/http/httpproxy · golang.org/x/net/proxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net Go |
|
|
| stdlib Go |
|
|
Go standard library net/http · golang.org/x/net/http/httpproxy · golang.org/x/net/proxy
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net Go |
|
|
| stdlib Go |
|
|
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.
From the CVE record · Go
Go's net/http and golang.org/x/net proxy packages can incorrectly treat an IPv6 zone ID as part of a hostname when matching NO_PROXY patterns. A request to a crafted IPv6 address can therefore bypass the configured proxy; the input does not specify authentication or user-interaction requirements.
Engineers using Go standard library versions before 1.23.7 or from 1.24.0 up to but not including 1.24.1, or golang.org/x/net versions before 0.36.0, should check their applications.