Vulnerabilities

If a site is loaded over a HTTPS connection but loads a favicon resource over HTTP, the mixed content warning is not displayed to users.

The internal WebBrowserPersist code does not use correct origin context for a resource being saved.

Some special resource URIs will cause a non-exploitable crash if loaded with optional parameters following a '?' in the parsed string.

When a new protocol handler is registered, the API accepts a title argument which can be used to mislead users about which domain is registering the new protocol.

By using the reflected URL in some special resource URIs, such as chrome:, it is possible to inject stylesheets and bypass Content Security Policy (CSP).

A WebExtension can request access to local files without the warning prompt stating that the extension will "Access your data for all websites" being displayed to the user.

A vulnerability where a WebExtension can run content scripts in disallowed contexts following navigation or other events.

By rewriting the Host: request headers using the webRequest API, a WebExtension can bypass domain restrictions through domain fronting.

A potential vulnerability was found in 32-bit builds where an integer overflow during the conversion of scripts to an internal UTF-16 representation could result in allocating a buffer too small for the conversion.

When manipulating user events in nested loops while opening a document through script, it is possible to trigger a potentially exploitable crash due to poor event handling.

Mozilla developers and community members reported memory safety bugs present in Firefox 62 and Firefox ESR 60.2.

Mozilla developers and community members reported memory safety bugs present in Firefox 62.