firefox vulnerabilities (Mageia)
1,592 vulnerabilities.
firefoxMageiaCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxMageiaAn attacker could have triggered a use-after-free condition when creating a WebRTC connection...8.8 HighfirefoxMageiaMemory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of...9.8 CriticalfirefoxMageiaThe error page for sites with invalid TLS certificates was missing the activation-delay Firefox...3.1 LowfirefoxMageiaMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 HighfirefoxMageiaWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 HighfirefoxMageiaAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 MediumfirefoxMageiaA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 MediumfirefoxMageiaA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 HighfirefoxMageiaAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 MediumfirefoxMageiaIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 MediumfirefoxMageiaMozilla developers Randell Jesup, Andrew Osmond, Sebastian Hengst, Andrew McCreight, and the...8.8 HighfirefoxMageiaFirefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be...8.8 HighfirefoxMageiaWhen handling the filename directive in the Content-Disposition header, the filename would be...8.8 HighfirefoxMageiaAn attacker could cause the memory manager to incorrectly free a pointer that addresses attacker...8.8 HighfirefoxMageiaFollowing a Garbage Collector compaction, weak maps may have been accessed before they were...6.5 MediumfirefoxMageiaA website could have obscured the fullscreen notification by using a combination of <code>window...4.3 MediumfirefoxMageiaUnexpected data returned from the Safe Browsing API could have led to memory corruption and a...6.5 MediumfirefoxMageiaMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 HighfirefoxMageiaDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 MediumfirefoxMageiaWhile implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic...8.8 HighfirefoxMageiaWhen accessing throttled streams, the count of available bytes needed to be checked in the...6.5 MediumfirefoxMageiaSometimes, when invalidating JIT code while following an iterator, the newly generated code could...6.5 MediumfirefoxMageiaMozilla developers Philipp and Gabriele Svelto reported memory safety bugs present in Firefox ESR...8.8 HighfirefoxMageiaMozilla developers Kershaw Chang and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighfirefoxMageiaWhen importing a SPKI RSA public key as ECDSA P-256, the key would be handled incorrectly causing...6.5 MediumfirefoxMageiaModule load requests that failed were not being checked as to whether or not they were cancelled...8.8 HighfirefoxMageiaAn invalid downcast from <code>nsTextNode</code> to <code>SVGElement</code> could have lead to...8.8 HighfirefoxMageiaCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxMageiaWhen encoding data from an <code>inputStream</code> in <code>xpcom</code> the size of the input...8.8 HighfirefoxMageiaA background script invoking <code>requestFullscreen</code> and then blocking the main thread...5.4 MediumfirefoxMageiaPermission prompts for opening external schemes were only shown for <code>ContentPrincipals</code...8.8 HighfirefoxMageiaThe <code>Content-Security-Policy-Report-Only</code> header could allow an attacker to leak a...6.5 MediumfirefoxMageiaAn attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary...8.8 HighfirefoxMageiaMemory safety bugs fixed in Firefox 109 and Firefox ESR 102.78.8 HighfirefoxMageiaCalls to console.log allowed bypassing Content Security Policy via format directive6.5 MediumfirefoxMageiaContent Security Policy wasn't being correctly applied to WebSockets in WebWorkers6.5 MediumfirefoxMageiaURL being dragged from cross-origin iframe into same tab triggers navigation6.5 MediumfirefoxMageiaArbitrary file read from GTK drag and drop on Linux6.5 MediumfirefoxMageiaBy confusing the browser, the fullscreen notification could have been delayed or suppressed,...4.3 MediumfirefoxMageiaAn out of date library (libusrsctp) contained vulnerabilities that could potentially be exploited...8.8 HighfirefoxMageiaA use-after-free in WebGL extensions could have led to a potentially exploitable crash. This...9.8 CriticalfirefoxMageiaAn optimization in WebGL was incorrect in some cases, and could have led to memory corruption and...8.8 HighfirefoxMageiaA missing check related to tex units could have led to a use-after-free and potentially...6.5 MediumfirefoxMageiaMozilla developers Randell Jesup, Valentin Gosu, Olli Pettay, and the Mozilla Fuzzing Team...8.8 HighfirefoxMageiaA file with a long filename could have had its filename truncated to remove the valid extension,...8.8 HighfirefoxMageiaAn attacker who compromised a content process could have partially escaped the sandbox to read...8.6 HighfirefoxMageiaMozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in...8.8 HighfirefoxMageiaUse tables inside of an iframe, an attacker could have caused iframe contents to be rendered...6.5 MediumfirefoxMageiaIf a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have...6.1 Medium- Show moreLoading…