RHSA-2022:0125

It was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox.

Applying a CSS filter effect could have accessed out of bounds memory.

Constructing audio sinks could have lead to a race condition when playing audio files and closing windows.

Malicious websites could have confused Firefox into showing the wrong origin when asking to launch a program and handling an external URL protocol.

Mozilla developers Calixte Denizet, Kershaw Chang, Christian Holler, Jason Kratzer, Gabriele Svelto, Tyson Smith, Simon Giesecke, and Steve Fink reported memory safety bugs present in Firefox 95 and Firefox ESR 91.4.

Certain network request objects were freed too early when releasing a network request handle.

When resizing a popup while requesting fullscreen access, the popup would have become unable to leave fullscreen mode.

After accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the certificate data could have lead to a crash.

Securitypolicyviolation events could have leaked cross-origin information for frame-ancestors violations.

When inserting text while in edit mode, some characters might have lead to out-of-bounds memory access causing a potentially exploitable crash.

Malicious websites could have tricked users into accepting launching a program to handle an external URL protocol.

When navigating from inside an iframe while requesting fullscreen access, an attacker-controlled tab could have made the browser unable to leave fullscreen mode.