Vulnerabilities

Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7.

Firefox for Android suffered from a time-of-check-time-of-use vulnerability that allowed a malicious application to read sensitive data from application directories.

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.

If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reported in the violation report; as opposed to the original frame URI.

As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure that the source file is the URL requested by the page, pre-redirects.

Context-specific code was included in a shared jump table; resulting in assertions being triggered in multithreaded wasm code.

When processing a redirect with a conflicting Referrer-Policy, Firefox would have adopted the redirect's Referrer-Policy.

One phishing tactic on the web is to provide a link with HTTP Auth.

When trying to load a cross-origin resource in an audio/video context a decoding error may have resulted, and the content of that error may have revealed information about the resource.

The DOMParser API did not properly process '<noscript>' elements for escaping.

The developer page about:memory has a Measure function for exploring what object types the browser has allocated and their sizes.

When accepting a malicious intent from other installed apps, Firefox for Android accepted manifests from arbitrary file paths and allowed declaring webapp manifests for other origins.