Vulnerabilities

If Firefox is installed to a user-writable directory, the Mozilla Maintenance Service would execute updater.exe from the install location with system privileges.

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.

Firefox did not reset the address bar after the beforeunload dialog was shown if the user chose to remain on the page.

When trying to load a non-video in an audio/video context the exact status code (200, 302, 404, 500, 412, 403, etc.) was disclosed via the MediaError Message.

When processing a MAR update file, after the signature has been validated, an invalid name length could result in a heap overflow, leading to memory corruption and potentially arbitrary code execution.

A lock was missing when accessing a data structure and importing certificate information into the trust database.

Mozilla developers reported memory safety bugs present in Firefox for Android 79.