firefox vulnerabilities (Red Hat)
2,057 vulnerabilities.
firefoxRed HatIf a site had been granted the permission to open popup windows, it could cause Select elements...6.1 MediumfirefoxRed HatA difference in the handling of StructFields and ArrayTypes in WASM could be used to trigger an...9.8 CriticalfirefoxRed HatThe JavaScript garbage collector could mis-color cross-compartment objects if OOM conditions were...9.8 CriticalfirefoxRed HatFirefox normally asks for confirmation before asking the operating system to find an application...7.5 HighfirefoxRed HatInternal browser event interfaces were exposed to web content when privileged EventHandler...8.8 HighfirefoxRed HatA potentially exploitable type confusion could be triggered when looking up a property name on an...9.8 CriticalfirefoxRed HatThe date picker could partially obscure security prompts. This could be used by a malicious site...6.5 MediumfirefoxRed HatIncorrect garbage collection interaction in IndexedDB could have led to a use-after-free. This...8.8 HighfirefoxRed HatUnexpected marking work at the start of sweeping could have led to a use-after-free. This...8.8 HighfirefoxRed HatANGLE failed to initialize parameters which lead to reading from uninitialized memory. This could...6.5 MediumfirefoxRed HatIt was possible for a web extension with minimal permissions to create a `StreamFilter` which...8.1 HighfirefoxRed HatFirefox adds web-compatibility shims in place of some tracking scripts blocked by Enhanced...6.1 MediumfirefoxRed HatEditor code failed to check an attribute value. This could have led to an out-of-bounds read....8.8 HighfirefoxRed HatIncomplete WebAssembly exception handing could have led to a use-after-free. This vulnerability...8.8 HighfirefoxRed HatA type confusion bug in WebAssembly could be leveraged by an attacker to potentially achieve code...8.8 HighfirefoxRed HatInsufficient checks when processing graphics shared memory could have led to memory corruption....9.6 CriticalfirefoxRed HatSelect options could obscure the fullscreen notification dialog. This could be used by a...6.5 MediumfirefoxRed HatType Confusion in Async Generators in Javascript Engine7.5 HighfirefoxRed HatMemory safety bugs fixed in Firefox 128, Firefox ESR 115.13, Thunderbird 128, and Thunderbird 115.137.5 HighfirefoxRed HatMemory corruption in thread creation7.4 HighfirefoxRed HatRace condition in permission assignment4.7 MediumfirefoxRed HatMemory corruption in the networking stack could have led to a potentially exploitable crash. This...7.5 HighfirefoxRed HatMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 HighfirefoxRed HatBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 HighfirefoxRed HatOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 MediumfirefoxRed HatBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 MediumfirefoxRed HatBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 MediumfirefoxRed HatIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 HighfirefoxRed HatMemory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of...8.8 HighfirefoxRed HatWhen saving a page to PDF, certain font styles could have led to a potential use-after-free crash...8.8 HighfirefoxRed HatWhen importing resources using Web Workers, error messages would distinguish the difference...5.9 MediumfirefoxRed HatA bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a...6.1 MediumfirefoxRed HatIf the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not...4.3 MediumfirefoxRed HatPDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF8.8 HighfirefoxRed HatMemory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug...8.1 HighfirefoxRed HatThere was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server...3.7 LowfirefoxRed HatIf an AlignedBuffer were assigned to itself, the subsequent self-move could result in an...4.0 MediumfirefoxRed HatOn 32-bit versions there were integer-overflows that led to an out-of-bounds-read that...5.9 MediumfirefoxRed HatThe JIT created incorrect code for arguments in certain cases. This led to potential use-after...7.8 HighfirefoxRed HatIn some code patterns the JIT incorrectly optimized switch statements and generated code with out...8.8 HighfirefoxRed HatGetBoundName could return the wrong version of an object when JIT optimizations were applied....7.5 HighfirefoxRed HatAn attacker was able to inject an event handler into a privileged object that would allow...8.4 HighfirefoxRed HatTo harden ICU against exploitation, the behavior for out-of-memory conditions was changed to...2.7 LowfirefoxRed HatMemory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. Some of...8.8 HighfirefoxRed HatIf an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have...8.1 HighfirefoxRed HatA missing delay on when pointer lock was used could have allowed a malicious page to trick a user...5.5 MediumfirefoxRed HatUsing a markup injection an attacker could have stolen nonce values. This could have been used to...6.1 MediumfirefoxRed HatThe permission prompt input delay could have expired while the window is not in focus, which made...6.1 MediumfirefoxRed Hat`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()...8.4 HighfirefoxRed HatReturn registers were overwritten which could have allowed an attacker to execute arbitrary code....8.1 High- Show moreLoading…