MozillaFirefox vulnerabilities (openSUSE)
3,079 vulnerabilities.
MozillaFirefoxopenSUSEInsufficient checks when processing graphics shared memory could have led to memory corruption....9.6 CriticalMozillaFirefoxopenSUSESelect options could obscure the fullscreen notification dialog. This could be used by a...6.5 MediumMozillaFirefoxopenSUSEMemory safety bugs fixed in Firefox 128 and Thunderbird 1288.8 HighMozillaFirefoxopenSUSEIncorrect listing of stack frames4.3 MediumMozillaFirefoxopenSUSEIncorrect listing of stack frames5.5 MediumMozillaFirefoxopenSUSECSP violation leakage when using devtools5.3 MediumMozillaFirefoxopenSUSEIncorrect handling of SameSite cookies9.8 CriticalMozillaFirefoxopenSUSEForm validation popups could block exiting full-screen mode4.3 MediumMozillaFirefoxopenSUSEMemory corruption in NSS8.8 HighMozillaFirefoxopenSUSECursor could be moved out of the viewport using pointerlock.4.3 MediumMozillaFirefoxopenSUSELeaving pointerlock by pressing the escape key could be prevented8.8 HighMozillaFirefoxopenSUSEOut-of-bounds read in clipboard component8.2 HighMozillaFirefoxopenSUSEFirefox Android missed activation delay to prevent tapjacking8.8 HighMozillaFirefoxopenSUSEMemory safety bugs fixed in Firefox 128, Firefox ESR 115.13, Thunderbird 128, and Thunderbird 115.137.5 HighMozillaFirefoxopenSUSEMemory corruption in thread creation7.4 HighMozillaFirefoxopenSUSEMemory corruption in NSS9.8 CriticalMozillaFirefoxopenSUSERace condition in permission assignment4.7 MediumMozillaFirefoxopenSUSEMemory corruption in WebGL API6.3 MediumMozillaFirefoxopenSUSEMozillaFirefox-50.1.0-1.1 on GA mediaNo scoreMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 126. Some of these bugs showed evidence of memory...9.8 CriticalMozillaFirefoxopenSUSEIn violation of spec, cookie prefixes such as `__Secure` were being ignored if they were not...9.8 CriticalMozillaFirefoxopenSUSEBy manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid...6.1 MediumMozillaFirefoxopenSUSEA website was able to detect when a user took a screenshot of a page using the built-in...4.3 MediumMozillaFirefoxopenSUSEIf an out-of-memory condition occurs at a specific point using allocations in the probabilistic...9.8 CriticalMozillaFirefoxopenSUSEAn attacker could have caused a use-after-free in the JavaScript engine to read memory in the...7.5 HighMozillaFirefoxopenSUSEIn addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay...4.3 MediumMozillaFirefoxopenSUSEIf a specific sequence of actions is performed when opening a new tab, the triggering principal...5.3 MediumMozillaFirefoxopenSUSEOn Windows, when using the 'Save As' functionality, an attacker could have tricked the browser...6.5 MediumMozillaFirefoxopenSUSEMemory corruption in the networking stack could have led to a potentially exploitable crash. This...7.5 HighMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 HighMozillaFirefoxopenSUSEBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 HighMozillaFirefoxopenSUSEOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 MediumMozillaFirefoxopenSUSEBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 MediumMozillaFirefoxopenSUSEBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 MediumMozillaFirefoxopenSUSEIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 HighMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory...9.8 CriticalMozillaFirefoxopenSUSEA file dialog shown while in full-screen mode could have resulted in the window remaining...8.2 HighMozillaFirefoxopenSUSEAn iterator stop condition was missing when handling WASM code in the built-in profiler,...5.9 MediumMozillaFirefoxopenSUSEThe `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing...6.5 MediumMozillaFirefoxopenSUSEWhen a network error occurred during page load, the prior content could have remained in view...7.5 HighMozillaFirefoxopenSUSEAn HTTP digest authentication nonce value was generated using `rand()` which could lead to...5.9 MediumMozillaFirefoxopenSUSEA memory allocation check was missing which would lead to a use-after-free if the allocation...8.6 HighMozillaFirefoxopenSUSEDifferent techniques existed to obscure the fullscreen notification in Firefox for Android. ...4.3 MediumMozillaFirefoxopenSUSEWeb application manifests were stored by using an insecure MD5 hash which allowed for a hash...8.1 HighMozillaFirefoxopenSUSEMultiple WebRTC threads could have claimed a newly connected audio input leading to use-after...9.8 CriticalMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of...8.8 HighMozillaFirefoxopenSUSEWhen saving a page to PDF, certain font styles could have led to a potential use-after-free crash...8.8 HighMozillaFirefoxopenSUSEWhen importing resources using Web Workers, error messages would distinguish the difference...5.9 MediumMozillaFirefoxopenSUSEA bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a...6.1 MediumMozillaFirefoxopenSUSEIf the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not...4.3 Medium- Show moreLoading…