358 results · Feed
-
Unscored —
Under certain circumstances, asynchronous functions could have caused a navigation to fail but expose the target URL. T…
-
Unscored —
An incorrect type conversion of sizes from 64bit to 32bit integers allowed an attacker to corrupt memory leading to a p…
-
Unscored —
By misusing a race in our notification code, an attacker could have forcefully hidden the notification for pages that h…
-
Unscored —
Failure to correctly record the location of live pointers across wasm instance calls resulted in a GC occurring within …
-
Unscored —
WebExtensions with the correct permissions were able to create and install ServiceWorkers for third-party websites that…
-
Unscored —
When invoking protocol handlers for external protocols, a supplied parameter URL containing spaces was not properly esc…
-
Unscored —
Using XMLHttpRequest, an attacker could have identified installed applications by probing error messages for loading ex…
-
Unscored —
Documents loaded with the CSP sandbox directive could have escaped the sandbox's script restriction by embedding additi…
-
Unscored —
When receiving a URL through a SEND intent, Firefox would have searched for the text, but subsequent usages of the addr…
-
Unscored —
Using the Location API in a loop could have caused severe application hangs and crashes. This vulnerability affects Thu…
-
Unscored —
It was possible to recreate previous cursor spoofing attacks against users with a zoomed native cursor. This vulnerabil…
-
Unscored —
Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers. This allowed for a…
-
Unscored —
Firefox for Android allowed navigations through the `intent://` protocol, which could be used to cause crashes and UI s…
-
Unscored —
Mixed-content checks were unable to analyze opaque origins which led to some mixed content being loaded. This vulnerabi…
-
Unscored —
When delegating navigations to the operating system, Firefox would accept the `mk` scheme which might allow attackers t…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some of these bugs showed e…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 91. Some of these bugs showed evidence of memory corr…
-
Unscored —
During operations on MessageTasks, a task may have been removed while it was still scheduled, resulting in memory corru…
-
Unscored —
Through use of reportValidity() and window.open(), a plain-text validation message could have been overlaid on another …
-
Unscored —
During process shutdown, a document could have caused a use-after-free of a languages service object, leading to memory…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 92. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some of these bugs showed ev…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some of these bugs showed ev…
-
Unscored —
Uninitialized memory in a canvas object could have caused an incorrect free() leading to memory corruption and a potent…
-
Unscored —
An issue present in lowering/register allocation could have led to obscure but deterministic register confusion failure…
-
Unscored —
Due to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object, resulting in the pote…
-
Unscored —
Firefox for Android could get stuck in fullscreen mode and not exit it even after normal interactions that should cause…
-
Unscored —
Instruction reordering resulted in a sequence of instructions that would cause an object to be incorrectly considered d…
-
Unscored —
A use-after-free vulnerability in media channels could have led to memory corruption and a potentially exploitable cras…
-
Unscored —
A suspected race condition when calling getaddrinfo led to memory corruption and a potentially exploitable crash. *Note…
-
Unscored —
After requesting multiple permissions, and closing the first permission panel, subsequent permission panels will be dis…
-
Unscored —
Firefox incorrectly treated an inline list-item element as a block element, resulting in an out of bounds read or memor…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12. Some of these bugs showed e…
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 90. Some of these bugs showed e…
-
Unscored —
A malicious webpage could have triggered a use-after-free, memory corruption, and a potentially exploitable crash. *Thi…
-
Unscored —
A use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library. Updating the library …
-
Unscored —
When network partitioning was enabled, e.g. as a result of Enhanced Tracking Protection settings, a TLS error page woul…
-
Unscored —
Through a series of DOM manipulations, a message, over which the attacker had control of the text but not HTML or forma…
-
Unscored —
Mozilla developers reported memory safety bugs present in code shared between Firefox and Thunderbird. Some of these bu…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 89. Some of these bugs showed evidence of memory corr…