1,430 results · Feed
-
Unscored —
Failure to correctly record the location of live pointers across wasm instance calls resulted in a GC occurring within …
-
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 —
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 —
Mozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some of these bugs showed e…
-
Unscored —
During operations on MessageTasks, a task may have been removed while it was still scheduled, resulting in memory corru…
-
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 —
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 —
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 —
A malicious webpage could have triggered a use-after-free, memory corruption, and a potentially exploitable crash. *Thi…
-
Unscored —
Mozilla developers reported memory safety bugs present in code shared between Firefox and Thunderbird. Some of these bu…
-
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 —
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 —
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 —
A transient execution vulnerability, named Floating Point Value Injection (FPVI) allowed an attacker to leak arbitrary …
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some of these bugs showed e…
-
Unscored —
Out of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to potentially perform o…
-
Unscored —
A texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the buffer used to unpack …
-
Unscored —
Using techniques that built on the slipstream research, a malicious webpage could have scanned both an internal network…
-
Unscored —
A malicious extension could have opened a popup window lacking an address bar. The title of the popup lacking an addres…
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 86 and Firefox ESR 78.8. Some o…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some of these bugs showed ev…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some of these bugs showed ev…
-
Unscored —
If a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking cross-origin informati…
-
Unscored —
Using the new logical assignment operators in a JavaScript switch statement could have caused a type confusion, leading…
-
Unscored —
Performing garbage collection on re-declared JavaScript variables resulted in a user-after-poison, and a potentially ex…
-
Unscored —
Further techniques that built on the slipstream research combined with a malicious webpage could have exposed both an i…
-
Unscored —
If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reporte…
-
Unscored —
As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure th…
-
Unscored —
When trying to load a cross-origin resource in an audio/video context a decoding error may have resulted, and the conte…