Mozilla

Thunderbird allowed the Text Direction Override Unicode Character in filenames. An email attachment could be incorrectly

During the worker lifecycle, a use-after-free condition could have occurred, which could have led to a potentially explo

The session restore helper crashed whenever there was no parameter sent to the message handler. This vulnerability affec

The permission request prompt from the site in the background tab was overlaid on top of the site in the foreground tab.

When Firefox is configured to block storage of all cookies, it was still possible to store data in localstorage by using

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

Memory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. Some of these bugs showed evidenc

A website could prevent a user from exiting full-screen mode via alert and prompt calls. This could lead to user confus

A use-after-free condition existed in `NotifyOnHistoryReload` where a `LoadingSessionHistoryEntry` object was freed and

Uploading files which contain symlinks may have allowed an attacker to trick a user into submitting sensitive data to a

The use of RTL Arabic characters in the address bar may have allowed for URL spoofing. This vulnerability affects Firefo

A website could have obscured the fullscreen notification by using an option element by introducing lag via an expensive

Insufficient validation in the Drag and Drop API in conjunction with social engineering, may have allowed an attacker to

When opening Diagcab files, Firefox did not warn the user that these files may contain malicious code. This vulnerabilit

A website could have obscured the fullscreen notification by using a URL with a scheme handled by an external program, s

Cross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in t

An attacker could have triggered a use-after-free condition when creating a WebRTC connection over HTTPS. This vulnerabi

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

Memory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of these bugs showed evidenc

When choosing a site-isolated process for a document loaded from a data: URL that was the result of a redirect, Firefox

The error page for sites with invalid TLS certificates was missing the activation-delay Firefox uses to protect prompts

When recording the screen while in Private Browsing on Firefox for Android the address bar and keyboard were not hidden,

Similar to CVE-2023-28163, this time when choosing 'Save Link As', suggested filenames containing environment variable n

A newline in a filename could have been used to bypass the file extension security mechanisms that replace malicious fil

Different techniques existed to obscure the fullscreen notification in Firefox and Focus for Android. These could have

A potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below versi

An invalid downcast from `nsHTMLDocument` to `nsIContent` could have lead to undefined behavior. This vulnerability affe

The return value from `gfx::SourceSurfaceSkia::Map()` wasn't being verified which could have potentially lead to a null

A compromised child process could have injected XBL Bindings into privileged CSS rules, resulting in arbitrary code exec

Mozilla developers and community members Ronald Crane, Andrew McCreight, Randell Jesup and the Mozilla Fuzzing Team repo

Protocol handlers `ms-cxh` and `ms-cxh-full` could have been leveraged to trigger a denial of service. *Note: This attac

Documents were incorrectly assuming an ordering of principal objects when ensuring we were loading an appropriately priv

A maliciously crafted favicon could have led to an out of memory crash. This vulnerability affects Firefox < 113.

Service workers could reveal script base URL due to dynamic `import()`. This vulnerability affects Firefox < 113.

A local attacker can trick the Mozilla Maintenance Service into applying an unsigned update file by pointing the service

An attacker could have caused an out of bounds memory access using WebGL APIs, leading to memory corruption and a potent

Mozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough, Sebastian Hengst, Andrew McCre

When reading a file, an uninitialized value could have been used as read limit. This vulnerability affects Firefox < 113

An attacker could have positioned a `datalist` element to obscure the address bar. This vulnerability affects Firefox <

A type checking bug would have led to invalid code being compiled. This vulnerability affects Firefox < 113, Firefox ESR

A missing delay in popup notifications could have made it possible for an attacker to trick a user into granting permiss

An out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability affects Firefox < 113, Fire

In multiple cases browser prompts could have been obscured by popups controlled by content. These could have led to pote

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

Memory safety bugs present in Firefox 111 and Firefox ESR 102.9. Some of these bugs showed evidence of memory corruption

Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. This may

A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result. This vulnerability affec

When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, w

If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused mem

An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global ob