RHSA-2020:4080

When recursing through graphical layers while scrolling, an iterator may have become invalid, resulting in a potential use-after-free.

Mozilla developers reported memory safety bugs present in Firefox 80 and Firefox ESR 78.2.

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.

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.

By exploiting an Open Redirect vulnerability on a website, an attacker could have spoofed the site displayed in the download file dialog to show the original site (the one suffering from the open redirect) rather than th…

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

Firefox sometimes ran the onload handler for SVG elements that the DOM sanitizer decided to remove, resulting in JavaScript being executed after pasting attacker-controlled data into a contenteditable element.