firefox vulnerabilities (Ubuntu)
1,530 vulnerabilities.
firefoxUbuntuLeaving pointerlock by pressing the escape key could be prevented8.8 HighfirefoxUbuntuOut-of-bounds read in clipboard component8.2 HighfirefoxUbuntuMemory safety bugs fixed in Firefox 128, Firefox ESR 115.13, Thunderbird 128, and Thunderbird 115.137.5 HighfirefoxUbuntuMemory corruption in thread creation7.4 HighfirefoxUbuntuMemory corruption in NSS9.8 CriticalfirefoxUbuntuRace condition in permission assignment4.7 MediumfirefoxUbuntuMemory safety bugs present in Firefox 126. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxUbuntuIn violation of spec, cookie prefixes such as `__Secure` were being ignored if they were not...9.8 CriticalfirefoxUbuntuBy manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid...6.1 MediumfirefoxUbuntuA website was able to detect when a user took a screenshot of a page using the built-in...4.3 MediumfirefoxUbuntuIf an out-of-memory condition occurs at a specific point using allocations in the probabilistic...9.8 CriticalfirefoxUbuntuAn attacker could have caused a use-after-free in the JavaScript engine to read memory in the...7.5 HighfirefoxUbuntuIn addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay...4.3 MediumfirefoxUbuntuMemory corruption in the networking stack could have led to a potentially exploitable crash. This...7.5 HighfirefoxUbuntuMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 HighfirefoxUbuntuBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 HighfirefoxUbuntuOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 MediumfirefoxUbuntuBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 MediumfirefoxUbuntuBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 MediumfirefoxUbuntuIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 HighfirefoxUbuntufirefox regressionsNo scorefirefoxUbuntuMemory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxUbuntuA file dialog shown while in full-screen mode could have resulted in the window remaining...8.2 HighfirefoxUbuntuAn iterator stop condition was missing when handling WASM code in the built-in profiler,...5.9 MediumfirefoxUbuntuThe `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing...6.5 MediumfirefoxUbuntuWhen a network error occurred during page load, the prior content could have remained in view...7.5 HighfirefoxUbuntuAn HTTP digest authentication nonce value was generated using `rand()` which could lead to...5.9 MediumfirefoxUbuntuA memory allocation check was missing which would lead to a use-after-free if the allocation...8.6 HighfirefoxUbuntuMultiple WebRTC threads could have claimed a newly connected audio input leading to use-after...9.8 CriticalfirefoxUbuntuMemory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of...8.8 HighfirefoxUbuntuWhen saving a page to PDF, certain font styles could have led to a potential use-after-free crash...8.8 HighfirefoxUbuntuWhen importing resources using Web Workers, error messages would distinguish the difference...5.9 MediumfirefoxUbuntuA bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a...6.1 MediumfirefoxUbuntuIf the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not...4.3 MediumfirefoxUbuntuPDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF8.8 HighfirefoxUbuntufirefox regressionsNo scorefirefoxUbuntuMemory safety bugs present in Firefox 124. Some of these bugs showed evidence of memory...8.1 HighfirefoxUbuntuMemory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug...8.1 HighfirefoxUbuntuThere was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server...3.7 LowfirefoxUbuntuThe MarkStack assignment operator, part of the JavaScript engine, could access uninitialized...5.3 MediumfirefoxUbuntuIf an AlignedBuffer were assigned to itself, the subsequent self-move could result in an...4.0 MediumfirefoxUbuntuAn out-of-memory condition during object initialization could result in an empty shape list. If...6.2 MediumfirefoxUbuntuOn 32-bit versions there were integer-overflows that led to an out-of-bounds-read that...5.9 MediumfirefoxUbuntuIt was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This...7.5 HighfirefoxUbuntuThe JIT created incorrect code for arguments in certain cases. This led to potential use-after...7.8 HighfirefoxUbuntuA use-after-free could occur during WASM execution if garbage collection ran during the creation...8.8 HighfirefoxUbuntuIn certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds...6.5 MediumfirefoxUbuntuIn some code patterns the JIT incorrectly optimized switch statements and generated code with out...8.8 HighfirefoxUbuntuA use-after-free could result if a JavaScript realm was in the process of being initialized when...7.5 HighfirefoxUbuntuGetBoundName could return the wrong version of an object when JIT optimizations were applied....7.5 High- Show moreLoading…