cbcvebase.

Go Standard Library Net Http vulnerabilities

24 known vulnerabilities affecting go_standard_library/net_http.

Total CVEs
24
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL2HIGH12MEDIUM10

Vulnerabilities

Page 2 of 2
CVE-2024-45336P4MEDIUMCVSS 6.1fixed in 1.22.11≥ 1.23.0-0, < 1.23.5+1 more2025-01-28
CVE-2024-45336 [MEDIUM] CVE-2024-45336: The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a requ The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain
nvd
CVE-2025-58186P4MEDIUMCVSS 5.3fixed in 1.24.8≥ 1.25.0, < 1.25.22025-10-29
CVE-2025-58186 [MEDIUM] CVE-2025-58186: Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does no Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.
nvd
CVE-2023-45289P4MEDIUMCVSS 4.3fixed in 1.21.8≥ 1.22.0-0, < 1.22.12024-03-05
CVE-2023-45289 [MEDIUM] CVE-2023-45289: When following an HTTP redirect to a domain which is not a subdomain match or exact match of the ini 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 redir
nvd
CVE-2025-22870P4MEDIUMCVSS 4.4fixed in 1.23.7≥ 1.24.0-0, < 1.24.12025-03-12
CVE-2025-22870 [MEDIUM] CWE-115 CVE-2025-22870: Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname componen 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.
nvd