firefox vulnerabilities (Red Hat)
2,057 vulnerabilities.
firefoxRed HatMemory safety bugs fixed in Firefox 117, Firefox ESR 115.2, and Thunderbird 115.28.8 HighfirefoxRed HatMemory safety bugs fixed in Firefox 117, Firefox ESR 102.15, Firefox ESR 115.2, Thunderbird 102.15, and Thunderbird 115.28.8 HighfirefoxRed HatBrowsing Context potentially not cleared when closing Private Window7.5 HighfirefoxRed HatXLL file extensions were downloadable without warnings4.3 MediumfirefoxRed HatPush notifications saved to disk unencrypted6.5 MediumfirefoxRed HatError reporting methods in SpiderMonkey could have triggered an Out of Memory Exception6.5 MediumfirefoxRed HatMemory corruption in JIT UpdateRegExpStatics6.5 MediumfirefoxRed HatMemory corruption in IPC FilePickerShownCallback6.5 MediumfirefoxRed HatMemory corruption in IPC ColorPickerShownCallback6.5 MediumfirefoxRed HatMemory corruption in IPC CanvasTranslator6.5 MediumfirefoxRed HatMemory safety bugs present in Firefox 115, Firefox ESR 115.0, and Thunderbird 115.0. Some of...9.8 CriticalfirefoxRed HatMemory safety bugs present in Firefox 115, Firefox ESR 115.0, Firefox ESR 102.13, Thunderbird 115...9.8 CriticalfirefoxRed HatWhen the number of cookies per domain was exceeded in `document.cookie`, the actual cookie jar...7.5 HighfirefoxRed HatFull screen notification obscured by external program6.5 MediumfirefoxRed HatFull screen notification obscured by file open dialog7.5 HighfirefoxRed HatIn some cases, an untrusted input stream was copied to a stack buffer without checking its size....7.5 HighfirefoxRed HatRace conditions in reference counting code were found through code inspection. These could have...5.9 MediumfirefoxRed HatAn out-of-bounds read could have led to an exploitable crash when parsing HTML with DOMParser in...7.5 HighfirefoxRed HatA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 HighfirefoxRed HatIn some circumstances, a stale value could have been used for a global variable in WASM JIT...5.3 MediumfirefoxRed HatOffscreen Canvas did not properly track cross-origin tainting, which could have been used to...5.3 MediumfirefoxRed HatUse-after-free in workers8.8 HighfirefoxRed HatMemory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. Some of...8.8 HighfirefoxRed HatWhen opening Diagcab files, Firefox did not warn the user that these files may contain malicious...7.8 HighfirefoxRed HatA website could have obscured the fullscreen notification by using a URL with a scheme handled by...6.5 MediumfirefoxRed HatCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxRed HatAn attacker could have triggered a use-after-free condition when creating a WebRTC connection...8.8 HighfirefoxRed HatMemory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of...9.8 CriticalfirefoxRed HatThe error page for sites with invalid TLS certificates was missing the activation-delay Firefox...3.1 LowfirefoxRed HatMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 HighfirefoxRed HatWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 HighfirefoxRed HatAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 MediumfirefoxRed HatA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 MediumfirefoxRed HatA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 HighfirefoxRed HatAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 MediumfirefoxRed HatIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 MediumfirefoxRed HatUse after free in libwebp5.3 MediumfirefoxRed HatMozilla developers Randell Jesup, Andrew Osmond, Sebastian Hengst, Andrew McCreight, and the...8.8 HighfirefoxRed HatA wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result....6.5 MediumfirefoxRed HatFirefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be...8.8 HighfirefoxRed HatWhen handling the filename directive in the Content-Disposition header, the filename would be...8.8 HighfirefoxRed HatAn attacker could cause the memory manager to incorrectly free a pointer that addresses attacker...8.8 HighfirefoxRed HatFollowing a Garbage Collector compaction, weak maps may have been accessed before they were...6.5 MediumfirefoxRed HatA website could have obscured the fullscreen notification by using a combination of <code>window...4.3 MediumfirefoxRed HatUnexpected data returned from the Safe Browsing API could have led to memory corruption and a...6.5 MediumfirefoxRed HatMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 HighfirefoxRed HatDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 MediumfirefoxRed HatWhile implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic...8.8 HighfirefoxRed HatWhen accessing throttled streams, the count of available bytes needed to be checked in the...6.5 MediumfirefoxRed HatSometimes, when invalidating JIT code while following an iterator, the newly generated code could...6.5 Medium- Show moreLoading…