RHSA-2021:1352

A WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out of bound write.

Ports that were written as an integer overflow above the bounds of a 16-bit integer could have bypassed port blocking restrictions when used in the Alt-Svc header.

If a Blob URL was loaded through some unusual user interaction, it could have been loaded by the System Principal and granted additional privileges that should not be granted to web content.

When a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the newlines would have been interpreted as such and allowed arbitrary commands to be sent to the FTP server.

When Responsive Design Mode was enabled, it used references to objects that were previously freed.

Further techniques that built on the slipstream research combined with a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine.

The WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read and result in a crash.

Through complicated navigations with new windows, an HTTP page could have inherited a secure lock icon from an HTTPS page.

Signatures are written to disk before and read during verification, which might be subject to a race condition when a malicious local process or user is replacing the file.