1,654 results · Feed
-
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 —
If a user had granted a permission to a webpage and saved that grant, any webpage running on the same host - irrespecti…
-
Unscored —
A use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library. Updating the library …
-
Unscored —
Password autofill was enabled without user interaction on insecure websites on Firefox for Android. This was corrected …
-
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…
-
Unscored —
A WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out of bound write. This vu…
-
Unscored —
When Responsive Design Mode was enabled, it used references to objects that were previously freed. We presume that with…
-
Unscored —
By utilizing 3D CSS in conjunction with Javascript, content could have been rendered outside the webpage's viewport, re…
-
Unscored —
Due to unexpected data type conversions, a use-after-free could have occurred when interacting with the font cache. We …
-
Unscored —
Through complicated navigations with new windows, an HTTP page could have inherited a secure lock icon from an HTTPS pa…
-
Unscored —
If a Blob URL was loaded through some unusual user interaction, it could have been loaded by the System Principal and g…
-
Unscored —
A race condition with requestPointerLock() and setTimeout() could have resulted in a user interacting with one tab when…
-
Unscored —
A compromised content process could have performed session history manipulations it should not have been able to due to…
-
Unscored —
When a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the newlines would have been int…
-
Unscored —
The WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read and result in a crash…
-
Unscored —
Ports that were written as an integer overflow above the bounds of a 16-bit integer could have bypassed port blocking r…
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 87. Some of these bugs showed e…
-
Unscored —
When Web Render components were destructed, a race condition could have caused undefined behavior, and we presume that …
-
Unscored —
A transient execution vulnerability, named Floating Point Value Injection (FPVI) allowed an attacker to leak arbitrary …
-
Unscored —
When a user has already allowed a website to access microphone and camera, disabling camera sharing would not fully pre…
-
Unscored —
Firefox used to cache the last filename used for printing a file. When generating a filename for printing, Firefox usua…