Improper handling of JavaScript whitespace in html/template
Not all valid JavaScript whitespace characters are considered to be whitespace.
OpenShift API for Data Protection (OADP) 1.1.5 security and bug fix update
Released 2023-06-29 · Red Hat rating Important · View on Red Hat →
Not all valid JavaScript whitespace characters are considered to be whitespace.
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.
A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.
Templates containing actions in unquoted HTML attributes (e.g.
Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts.