358 results · Feed
-
Critical 9.8
Data race in crossbeam-deque
crossbeam-deque is a package of work-stealing deques for building task schedulers when programming in Rust. In versions prior to 0.7.4 and 0.8.0, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of oth…
-
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 —
Lack of escaping allowed HTML injection when a webpage was viewed in Reader View. While a Content Security Policy preve…
-
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 —
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…
-
Unscored —
When styling and rendering an oversized `<select>` element, Firefox did not apply correct clipping which allowed an att…
-
Unscored —
Firefox for Android would become unstable and hard-to-recover when a website opened too many popups. *This bug only aff…
-
Unscored —
Address bar search suggestions in private browsing mode were re-using session data from normal mode. *This bug only aff…
-
Unscored —
A malicious website that causes an HTTP Authentication dialog to be spawned could trick the built-in password manager t…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 88. Some of these bugs showed evidence of memory corr…
-
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 —
By causing a transition on a parent node by removing a CSS rule, an invalid property for a marker could have been appli…
-
Unscored —
A malicious extension could have opened a popup window lacking an address bar. The title of the popup lacking an addres…
-
Unscored —
If an attacker is able to alter specific about:config values (for example malware running on the user's computer), the …
-
Unscored —
A malicious extension with the 'search' permission could have installed a new search engine whose favicon referenced a …
-
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 86. Some of these bugs showed evidence of memory corr…
-
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 84. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 85. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some of these bugs showed ev…
-
Unscored —
Firefox for Android suffered from a time-of-check-time-of-use vulnerability that allowed a malicious application to rea…
-
Unscored —
When sharing geolocation during an active WebRTC share, Firefox could have reset the webRTC sharing state in the user i…
-
Unscored —
Using the new logical assignment operators in a JavaScript switch statement could have caused a type confusion, leading…
-
Unscored —
The browser could have been confused into transferring a pointer lock state into another tab, which could have lead to …