Stack exhaustion in Decoder.Decode in encoding/gob
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.
Control plane Operators for RHOSO 18.0.3 (Feature Release 1) security update
Released 2024-11-13 · Red Hat rating Important · View on Red Hat →
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.
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.
If errors returned from MarshalJSON methods contain user controlled data, they may be used to break the contextual auto-escaping behavior of the html/template package, allowing for subsequent actions to inject unexpected…
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
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".