4.3
Moyenne
CVE-2023-45289 When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an…
Description
When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as "Authorization" or "Cookie". For example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly forwarded.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| net/http 1.22 | 1.22.0-0 → < 1.22.1 | 1.22.1 |
| net/http 1.21 | premières → < 1.21.8 | 1.21.8 |
| net/http/cookiejar 1.22 | 1.22.0-0 → < 1.22.1 | 1.22.1 |
| net/http/cookiejar 1.21 | premières → < 1.21.8 | 1.21.8 |
Références
- go.dev go.dev
- go.dev go.dev
- groups.google.com groups.google.com
- pkg.go.dev pkg.go.dev
- security.netapp.com security.netapp.com
- www.openwall.com www.openwall.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de net/http
Les 26 CVE de net/http →
CVE-2026-97032
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently
7.5
Élevée
CVE-2026-78663
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream…
9.1
Critique
CVE-2026-78669
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams…
7.5
Élevée
CVE-2026-78667
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS)…
7.5
Élevée