firefox vulnerabilities (openEuler)
1,191 vulnerabilities.
firefoxopenEulerMemory corruption in NSS9.8 CriticalfirefoxopenEulerRace condition in permission assignment4.7 MediumfirefoxopenEulerMemory safety bugs present in Firefox 126. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxopenEulerIn violation of spec, cookie prefixes such as `__Secure` were being ignored if they were not...9.8 CriticalfirefoxopenEulerBy manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid...6.1 MediumfirefoxopenEulerA website was able to detect when a user took a screenshot of a page using the built-in...4.3 MediumfirefoxopenEulerIf an out-of-memory condition occurs at a specific point using allocations in the probabilistic...9.8 CriticalfirefoxopenEulerAn attacker could have caused a use-after-free in the JavaScript engine to read memory in the...7.5 HighfirefoxopenEulerIn addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay...4.3 MediumfirefoxopenEulerOn Windows, when using the 'Save As' functionality, an attacker could have tricked the browser...6.5 MediumfirefoxopenEulerMemory corruption in the networking stack could have led to a potentially exploitable crash. This...7.5 HighfirefoxopenEulerMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 HighfirefoxopenEulerBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 HighfirefoxopenEulerOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 MediumfirefoxopenEulerBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 MediumfirefoxopenEulerBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 MediumfirefoxopenEulerIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 HighfirefoxopenEulerMemory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxopenEulerA file dialog shown while in full-screen mode could have resulted in the window remaining...8.2 HighfirefoxopenEulerAn iterator stop condition was missing when handling WASM code in the built-in profiler,...5.9 MediumfirefoxopenEulerThe `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing...6.5 MediumfirefoxopenEulerWhen a network error occurred during page load, the prior content could have remained in view...7.5 HighfirefoxopenEulerAn HTTP digest authentication nonce value was generated using `rand()` which could lead to...5.9 MediumfirefoxopenEulerA memory allocation check was missing which would lead to a use-after-free if the allocation...8.6 HighfirefoxopenEulerMultiple WebRTC threads could have claimed a newly connected audio input leading to use-after...9.8 CriticalfirefoxopenEulerMemory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of...8.8 HighfirefoxopenEulerWhen saving a page to PDF, certain font styles could have led to a potential use-after-free crash...8.8 HighfirefoxopenEulerWhen importing resources using Web Workers, error messages would distinguish the difference...5.9 MediumfirefoxopenEulerA bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a...6.1 MediumfirefoxopenEulerIf the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not...4.3 MediumfirefoxopenEulerPDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF8.8 HighfirefoxopenEulerMemory safety bugs present in Firefox 124. Some of these bugs showed evidence of memory...8.1 HighfirefoxopenEulerMemory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug...8.1 HighfirefoxopenEulerThere was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server...3.7 LowfirefoxopenEulerThe MarkStack assignment operator, part of the JavaScript engine, could access uninitialized...5.3 MediumfirefoxopenEulerIf an AlignedBuffer were assigned to itself, the subsequent self-move could result in an...4.0 MediumfirefoxopenEulerAn out-of-memory condition during object initialization could result in an empty shape list. If...6.2 MediumfirefoxopenEulerOn 32-bit versions there were integer-overflows that led to an out-of-bounds-read that...5.9 MediumfirefoxopenEulerIt was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This...7.5 HighfirefoxopenEulerThe JIT created incorrect code for arguments in certain cases. This led to potential use-after...7.8 HighfirefoxopenEulerA use-after-free could occur during WASM execution if garbage collection ran during the creation...8.8 HighfirefoxopenEulerIn certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds...6.5 MediumfirefoxopenEulerIn some code patterns the JIT incorrectly optimized switch statements and generated code with out...8.8 HighfirefoxopenEulerA use-after-free could result if a JavaScript realm was in the process of being initialized when...7.5 HighfirefoxopenEulerGetBoundName could return the wrong version of an object when JIT optimizations were applied....7.5 HighfirefoxopenEulerAn attacker was able to inject an event handler into a privileged object that would allow...8.4 HighfirefoxopenEulerAn attacker was able to perform an out-of-bounds read or write on a JavaScript object by fooling...9.8 CriticalfirefoxopenEulerTo harden ICU against exploitation, the behavior for out-of-memory conditions was changed to...2.7 LowfirefoxopenEulerMemory safety bugs present in Firefox 123. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxopenEulerMemory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. Some of...8.8 High- Show moreLoading…