firefox-l10n vulnerabilities (Mageia)
1,579 vulnerabilities.
firefox-l10nMageiaDuring iframe navigation, certain pages did not have their FeaturePolicy fully initialized...6.5 Mediumfirefox-l10nMageiaBy injecting a cookie with certain special characters, an attacker on a shared subdomain which is...6.5 Mediumfirefox-l10nMageiaWhen injecting an HTML base element, some requests would ignore the CSP's base-uri settings and...6.1 Mediumfirefox-l10nMageiaMembers the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR...8.8 Highfirefox-l10nMageiaA cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions ...8.8 Highfirefox-l10nMageiaAn attacker could have abused XSLT error handling to associate attacker-controlled content with...6.5 Mediumfirefox-l10nMageiaWhen combining CSS properties for overflow and transform, the mouse cursor could interact with...7.5 Highfirefox-l10nMageiaWhen visiting directory listings for `chrome://` URLs as source text, some parameters were...5.3 Mediumfirefox-l10nMageiaThe Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of...8.8 Highfirefox-l10nMageiaIn the <code>nsTArray_Impl::ReplaceElementsAt()</code> function, an integer overflow could have...8.8 Highfirefox-l10nMageiaA malicious website that could create a popup could have resized the popup to overlay the address...6.5 Mediumfirefox-l10nMageiaIf there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests...4.3 Mediumfirefox-l10nMageiaSession history navigations may have led to a use-after-free and potentially exploitable crash....9.8 Criticalfirefox-l10nMageiaAn iframe that was not permitted to run scripts could do so if the user clicked on a <code...8.8 Highfirefox-l10nMageiaIf an object prototype was corrupted by an attacker, they would have been able to set undesired...8.8 Highfirefox-l10nMageiaMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 Criticalfirefox-l10nMageiaAn attacker could have injected CSS into stylesheets accessible via internal URIs, such as...6.5 Mediumfirefox-l10nMageiaAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 Mediumfirefox-l10nMageiaA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 Highfirefox-l10nMageiaOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 Highfirefox-l10nMageiaWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 Mediumfirefox-l10nMageiaA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 Criticalfirefox-l10nMageiaA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 Criticalfirefox-l10nMageiaIf an attacker was able to corrupt the methods of an Array object in JavaScript via prototype...8.8 Highfirefox-l10nMageiaAn attacker could have sent a message to the parent process where the contents were used to...8.8 Highfirefox-l10nMageiaMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 Criticalfirefox-l10nMageiaFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 Mediumfirefox-l10nMageiaWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 Mediumfirefox-l10nMageiaRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 Mediumfirefox-l10nMageiaAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 Mediumfirefox-l10nMageiaDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 Highfirefox-l10nMageiaMozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the...8.8 Highfirefox-l10nMageiaDue to a layout change, iframe contents could have been rendered outside of its border. This...5.4 Mediumfirefox-l10nMageiaWhen generating the assembly code for <code>MLoadTypedArrayElementHole</code>, an incorrect...6.5 Mediumfirefox-l10nMageiaBy using a link with <code>rel="localization"</code> a use-after-free could have been triggered...6.5 Mediumfirefox-l10nMageiaIf a compromised content process sent an unexpected number of WebAuthN Extensions in a Register...8.8 Highfirefox-l10nMageiaAfter a VR Process is destroyed, a reference to it may have been retained and used, leading to a...6.5 Mediumfirefox-l10nMageia<code>NSSToken</code> objects were referenced via direct points, and could have been accessed in...6.5 Mediumfirefox-l10nMageiaWhen installing an add-on, Firefox verified the signature before prompting the user; but while...7.5 Highfirefox-l10nMageiaPreviously Firefox for macOS and Linux would download temporary files to a user-specific...6.5 Mediumfirefox-l10nMageiaIf an attacker could control the contents of an iframe sandboxed with <code>allow-popups</code>...9.6 Criticalfirefox-l10nMageiaWhen resizing a popup after requesting fullscreen access, the popup would not display the...4.3 Mediumfirefox-l10nMageiaAn attacker could have caused a use-after-free by forcing a text reflow in an SVG object leading...8.8 Highfirefox-l10nMageiaRegular expression denial of service in Rust's regex crate7.5 Highfirefox-l10nMageiaAn unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable...9.6 Criticalfirefox-l10nMageiaRemoving an XSLT parameter during processing could have lead to an exploitable use-after-free. We...8.8 Highfirefox-l10nMageiaIn Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.9.8 Criticalfirefox-l10nMageiaxmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator...9.8 Criticalfirefox-l10nMageiaxmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as...9.8 Criticalfirefox-l10nMageiaMozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 High- Show moreLoading…