firefox vulnerabilities (Red Hat)
2,057 vulnerabilities.
firefoxRed HatA use-after-free vulnerability in media channels could have led to memory corruption and a...8.8 HighfirefoxRed HatInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 HighfirefoxRed HatUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 HighfirefoxRed HatData race in crossbeam-deque9.8 CriticalfirefoxRed HatMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighfirefoxRed HatA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighfirefoxRed HatOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighfirefoxRed HatMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighfirefoxRed HatPorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 HighfirefoxRed HatThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 MediumfirefoxRed HatWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 HighfirefoxRed HatIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 HighfirefoxRed HatThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 MediumfirefoxRed HatWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 HighfirefoxRed HatA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 HighfirefoxRed HatAn out of date graphics library (Angle) likely contained vulnerabilities that could potentially...9.8 CriticalfirefoxRed HatMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighfirefoxRed HatA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumfirefoxRed HatUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumfirefoxRed HatA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighfirefoxRed HatMozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some...8.8 HighfirefoxRed HatWhen trying to load a cross-origin resource in an audio/video context a decoding error may have...6.5 MediumfirefoxRed HatAs specified in the W3C Content Security Policy draft, when creating a violation report, "User...4.3 MediumfirefoxRed HatIf Content Security Policy blocked frame navigation, the full destination of a redirect served in...4.3 MediumfirefoxRed HatMozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some...8.8 HighfirefoxRed HatFurther techniques that built on the slipstream research combined with a malicious webpage could...7.4 HighfirefoxRed HatPerforming garbage collection on re-declared JavaScript variables resulted in a user-after-poison...8.8 HighfirefoxRed HatUsing the new logical assignment operators in a JavaScript switch statement could have caused a...8.8 HighfirefoxRed HatIf a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking...4.3 MediumfirefoxRed HatUse after free in WebRTC in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to...8.8 HighfirefoxRed HatMozilla developers reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. Some...8.8 HighfirefoxRed HatWhen an extension with the proxy permission registered to receive <all_urls>, the proxy.onRequest...4.3 MediumfirefoxRed HatUsing techniques that built on the slipstream research, a malicious webpage could have exposed...6.1 MediumfirefoxRed HatWhen a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the...6.5 MediumfirefoxRed HatWhen flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been...8.8 HighfirefoxRed HatCertain input to the CSS Sanitizer confused it, resulting in incorrect components being removed....8.8 HighfirefoxRed HatCertain blit values provided by the user were not properly constrained leading to a heap buffer...8.8 HighfirefoxRed HatUninitialized Use in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to...6.5 MediumfirefoxRed HatMozilla developers reported memory safety bugs present in Firefox 82 and Firefox ESR 78.4. Some...8.8 HighfirefoxRed HatSome websites have a feature "Show Password" where clicking a button will change a password field...6.5 MediumfirefoxRed HatWhen DNS over HTTPS is in use, it intentionally filters RFC1918 and related IP ranges from the...6.5 MediumfirefoxRed HatIf the Compact() method was called on an nsTArray, the array could have been reallocated without...8.8 HighfirefoxRed HatDuring browser shutdown, reference decrementing could have occured on a previously freed object,...8.8 HighfirefoxRed HatFirefox did not block execution of scripts with incorrect MIME types when the response was...6.1 MediumfirefoxRed HatIn some cases, removing HTML elements during sanitization would keep existing SVG event handlers...6.1 MediumfirefoxRed HatIt was possible to cause the browser to enter fullscreen mode without displaying the security UI;...4.3 MediumfirefoxRed HatA parsing and event loading mismatch in Firefox's SVG code could have allowed load events to fire...6.1 MediumfirefoxRed HatSide-channel information leakage in graphics in Google Chrome prior to 87.0.4280.66 allowed a...4.3 MediumfirefoxRed HatIn certain circumstances, the MCallGetProperty opcode can be emitted with unmet assumptions...8.8 HighfirefoxRed HatMozilla developers and community members reported memory safety bugs present in Firefox 81 and...9.8 Critical- Show moreLoading…