firefox vulnerabilities (Mageia)
1,592 vulnerabilities.
firefoxMageiaKeyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread...6.5 MediumfirefoxMageiaWhen resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be...8.8 HighfirefoxMageiaCross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing...6.1 MediumfirefoxMageiaWhen a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the...6.5 MediumfirefoxMageiaThe garbage collector could have been aborted in several states and zones and <code>GCRuntime:...8.8 HighfirefoxMageiaThrough a series of popups that reuse windowName, an attacker can cause a window to go fullscreen...6.5 MediumfirefoxMageiaIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may...9.8 CriticalfirefoxMageiaFreeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have...6.5 MediumfirefoxMageiaThrough a series of popup and <code>window.print()</code> calls, an attacker can cause a window...6.5 MediumfirefoxMageiaService Workers should not be able to infer information about opaque cross-origin responses; but...6.5 MediumfirefoxMageiaIn libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared...7.5 HighfirefoxMageiaMozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighfirefoxMageiaIf a website called <code>window.print()</code> in a particular way, it could cause a denial of...6.5 MediumfirefoxMageiaCertain types of allocations were missing annotations that, if the Garbage Collector was in a...8.8 HighfirefoxMageiaA same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking...8.1 HighfirefoxMageiaA vulnerability found in nss. By this security vulnerability, nss client auth crash without a...7.5 HighfirefoxMageiaMozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the...8.8 HighfirefoxMageiaConcurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a...6.5 MediumfirefoxMageiaDuring iframe navigation, certain pages did not have their FeaturePolicy fully initialized...6.5 MediumfirefoxMageiaBy injecting a cookie with certain special characters, an attacker on a shared subdomain which is...6.5 MediumfirefoxMageiaWhen injecting an HTML base element, some requests would ignore the CSP's base-uri settings and...6.1 MediumfirefoxMageialibexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.8.1 HighfirefoxMageiaMembers the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR...8.8 HighfirefoxMageiaA cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions ...8.8 HighfirefoxMageiaAn attacker could have abused XSLT error handling to associate attacker-controlled content with...6.5 MediumfirefoxMageiaWhen combining CSS properties for overflow and transform, the mouse cursor could interact with...7.5 HighfirefoxMageiaWhen visiting directory listings for `chrome://` URLs as source text, some parameters were...5.3 MediumfirefoxMageiaThe Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of...8.8 HighfirefoxMageiaIn the <code>nsTArray_Impl::ReplaceElementsAt()</code> function, an integer overflow could have...8.8 HighfirefoxMageiaA malicious website that could create a popup could have resized the popup to overlay the address...6.5 MediumfirefoxMageiaIf there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests...4.3 MediumfirefoxMageiaSession history navigations may have led to a use-after-free and potentially exploitable crash....9.8 CriticalfirefoxMageiaAn iframe that was not permitted to run scripts could do so if the user clicked on a <code...8.8 HighfirefoxMageiaIf an object prototype was corrupted by an attacker, they would have been able to set undesired...8.8 HighfirefoxMageiaMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 CriticalfirefoxMageiaAn attacker could have injected CSS into stylesheets accessible via internal URIs, such as...6.5 MediumfirefoxMageiaAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 MediumfirefoxMageiaA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 HighfirefoxMageiaOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 HighfirefoxMageiaWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 MediumfirefoxMageiaA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 CriticalfirefoxMageiaA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 CriticalfirefoxMageiaIf an attacker was able to corrupt the methods of an Array object in JavaScript via prototype...8.8 HighfirefoxMageiaAn attacker could have sent a message to the parent process where the contents were used to...8.8 HighfirefoxMageiaMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 CriticalfirefoxMageiaFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 MediumfirefoxMageiaWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 MediumfirefoxMageiaRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 MediumfirefoxMageiaAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 MediumfirefoxMageiaDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 High- Show moreLoading…