firefox vulnerabilities (Mageia)
1,592 vulnerabilities.
firefoxMageiaBy displaying a form validity message in the correct location at the same time as a permission...4.3 MediumfirefoxMageiaThe Opportunistic Encryption feature of HTTP2 (RFC 8164) allows a connection to be transparently...6.5 MediumfirefoxMageiaThrough a series of navigations, Firefox could have entered fullscreen mode without notification...4.3 MediumfirefoxMageiaWhen interacting with an HTML input element's file picker dialog with webkitdirectory set, a use...8.8 HighfirefoxMageiaThe iframe sandbox rules were not correctly applied to XSLT stylesheets, allowing an iframe to...10.0 CriticalfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighfirefoxMageiaDuring process shutdown, a document could have caused a use-after-free of a languages service...7.5 HighfirefoxMageiaThrough use of reportValidity() and window.open(), a plain-text validation message could have...6.5 MediumfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighfirefoxMageiaDuring operations on MessageTasks, a task may have been removed while it was still scheduled,...8.8 HighfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some...8.8 HighfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12. Some...8.8 HighfirefoxMageiaFirefox incorrectly treated an inline list-item element as a block element, resulting in an out...8.8 HighfirefoxMageiaA suspected race condition when calling getaddrinfo led to memory corruption and a potentially...8.1 HighfirefoxMageiaA use-after-free vulnerability in media channels could have led to memory corruption and a...8.8 HighfirefoxMageiaInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 HighfirefoxMageiaUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 HighfirefoxMageiaData race in crossbeam-deque9.8 CriticalfirefoxMageiaMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighfirefoxMageiaA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighfirefoxMageiaOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighfirefoxMageiaPorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 HighfirefoxMageiaThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 MediumfirefoxMageiaWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 HighfirefoxMageiaIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 HighfirefoxMageiaThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 MediumfirefoxMageiaWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 HighfirefoxMageiaA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 HighfirefoxMageiaAn out of date graphics library (Angle) likely contained vulnerabilities that could potentially...9.8 CriticalfirefoxMageiaMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighfirefoxMageiaA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumfirefoxMageiaUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumfirefoxMageiaA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some...8.8 HighfirefoxMageiaWhen trying to load a cross-origin resource in an audio/video context a decoding error may have...6.5 MediumfirefoxMageiaAs specified in the W3C Content Security Policy draft, when creating a violation report, "User...4.3 MediumfirefoxMageiaIf Content Security Policy blocked frame navigation, the full destination of a redirect served in...4.3 MediumfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some...8.8 HighfirefoxMageiaFurther techniques that built on the slipstream research combined with a malicious webpage could...7.4 HighfirefoxMageiaPerforming garbage collection on re-declared JavaScript variables resulted in a user-after-poison...8.8 HighfirefoxMageiaUsing the new logical assignment operators in a JavaScript switch statement could have caused a...8.8 HighfirefoxMageiaIf a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking...4.3 MediumfirefoxMageiaUse after free in WebRTC in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to...8.8 HighfirefoxMageiaMozilla developers reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. Some...8.8 HighfirefoxMageiaWhen an extension with the proxy permission registered to receive <all_urls>, the proxy.onRequest...4.3 MediumfirefoxMageiaUsing techniques that built on the slipstream research, a malicious webpage could have exposed...6.1 MediumfirefoxMageiaWhen a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the...6.5 MediumfirefoxMageiaWhen flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been...8.8 HighfirefoxMageiaCertain input to the CSS Sanitizer confused it, resulting in incorrect components being removed....8.8 High- Show moreLoading…