Denial of service due to improper 100-continue handling in net/http
The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status.
container-tools:rhel8 security update
Released 2024-09-24 · Red Hat rating Moderate · View on Red Hat →
The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status.
The ParseAddressList function incorrectly handles comments (text within parentheses) within display names.
When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not app…
A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop.
Verifying a certificate chain which contains a certificate with an unknown public key algorithm will cause Certificate.Verify to panic.