Mozilla

A phishing site could have repurposed an `about:` dialog to show phishing content with an incorrect origin in the addres

A compromised content process could have updated the document URI. This could have allowed an attacker to set an arbitra

When a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have overr

A Linux user opening the print preview dialog could have caused the browser to crash. This vulnerability affects Firefox

The WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have led to a potentially ex

In some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could have led to an exploit

An unchecked return value in TLS handshake code could have caused a potentially exploitable crash. This vulnerability af

It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due to

An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable cr

An attacker could execute unauthorized script on a legitimate site through UXSS using window.open() by opening a javascr

Using a javascript: URI with a setTimeout race condition, an attacker can execute unauthorized scripts on top origin sit

Memory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory corruption and we presume that w

Browser tab titles were being leaked by GNOME to system logs. This could potentially expose the browsing habits of users

Under certain conditions, Firefox did not display a warning when a user attempted to navigate to a new protocol handler.

Applications which spawn a Toast notification in a background thread may have obscured fullscreen notifications displaye

A `<dialog>` element could have been manipulated to paint content outside of a sandboxed iframe. This could allow unt

In some instances, the user-agent would allow push requests which lacked a valid VAPID even though the push manager subs

The timing of a button click causing a popup to disappear was approximately the same length as the anti-clickjacking del

TypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in other APIs which expect Ty

`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only be abused in order to wr

Memory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5. Some of these bugs showed evidence

The `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on a dynamic type that la

A use-after-free was identified in the `nsDNSService::Init`. This issue appears to manifest rarely during start-up. Thi

The `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in headless mode. This vu

The `VideoBridge` allowed any content process to use textures produced by remote decoders. This could be abused to esca

A use-after-free condition affected TLS socket creation when under memory pressure. This vulnerability affects Firefox E

Firefox was susceptible to a heap buffer overflow in `nsTextFragment` due to insufficient OOM handling. This vulnerabili

When resolving a symlink, a race may occur where the buffer passed to `readlink` may actually be smaller than necessary.

The WebGL `DrawElementsInstanced` method was susceptible to a heap buffer overflow when used on systems with the Mesa VM

Multiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This attack could potentially all

When processing a PGP/MIME payload that contains digitally signed text, the first paragraph of the text was never shown

The signature of a digitally signed S/MIME email message may optionally specify the signature creation date and time. If

The NSS code used for checking PKCS#1 v1.5 was leaking information useful in mounting Bleichenbacher-like attacks. Both

Memory safety bugs present in Firefox 119. Some of these bugs showed evidence of memory corruption and we presume that w

Memory safety bugs present in Firefox 119, Firefox ESR 115.4, and Thunderbird 115.4. Some of these bugs showed evidence

If an attacker needed a user to load an insecure http: page and knew that user had enabled HTTPS-only mode, the attacker

When an https: web page created a pop-up from a "javascript:" URL, that pop-up was incorrectly allowed to load blockable

Relative URLs starting with three slashes were incorrectly parsed, and a path-traversal "/../" part in the path could be

When using X11, text selected by the page using the Selection API was erroneously copied into the primary selection, a t

Ownership mismanagement led to a use-after-free in ReadableByteStreams This vulnerability affects Firefox < 120, Firefox

The black fade animation when exiting fullscreen is roughly the length of the anti-clickjacking delay on permission prom

It was possible to cause the use of a MessagePort after it had already been freed, which could potentially have led to a

On some systems—depending on the graphics settings and drivers—it was possible to force an out-of-bounds read and leak m

An attacker could have performed HTML template injection via Reader Mode and exfiltrated user information. This vulnerab

An attacker could have accessed internal pages or data by ex-filtrating a security key from ReaderMode via the `referrer

When opening a page in reader mode, the redirect URL could have caused attacker-controlled script to execute in a reflec

An attacker could have created a malicious link using bidirectional characters to spoof the location in the address bar

Memory safety bugs present in Firefox 118. Some of these bugs showed evidence of memory corruption and we presume that w

Memory safety bugs present in Firefox 118, Firefox ESR 115.3, and Thunderbird 115.3. Some of these bugs showed evidence

A malicious web site can enter fullscreen mode while simultaneously triggering a WebAuthn prompt. This could have obscur