RHSA-2020:3555

In non-standard configurations, a JPEG image created by JavaScript could have caused an internal variable to overflow, resulting in an out of bounds write, memory corruption, and a potentially exploitable crash.

JIT optimizations involving the Javascript arguments object could confuse later optimizations.

When aborting an operation, such as a fetch, an abort signal may be deleted while alerting the objects to be notified.

By holding a reference to the eval() function from an about:blank window, a malicious webpage could have gained access to the InstallTrigger object which would allow them to prompt the user to install an extension.

The code for downloading files did not properly take care of special characters, which led to an attacker being able to cut off the file ending at an earlier position, leading to a different file type being downloaded th…

When in an endless loop, a website specifying a custom cursor using CSS could make it look like the user is interacting with the user interface, when they are not.

An iframe sandbox element with the allow-popups flag could be bypassed when using noopener links.

Due to confusion processing a hyphen character in Date.parse(), a one-byte out of bounds read could have occurred, leading to potential information disclosure.

When constructing a permission prompt for WebRTC, a URI was supplied from the content process.

Using object or embed tags, it was possible to frame other websites, even if they disallowed framing using the X-Frame-Options header.