nss vulnerabilities (Mageia)
1,368 vulnerabilities.
nssMageiaIf a website called <code>window.print()</code> in a particular way, it could cause a denial of...6.5 MediumnssMageiaCertain types of allocations were missing annotations that, if the Garbage Collector was in a...8.8 HighnssMageiaA same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking...8.1 HighnssMageiaA vulnerability found in nss. By this security vulnerability, nss client auth crash without a...7.5 HighnssMageiaMozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the...8.8 HighnssMageiaConcurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a...6.5 MediumnssMageiaDuring iframe navigation, certain pages did not have their FeaturePolicy fully initialized...6.5 MediumnssMageiaBy injecting a cookie with certain special characters, an attacker on a shared subdomain which is...6.5 MediumnssMageiaWhen injecting an HTML base element, some requests would ignore the CSP's base-uri settings and...6.1 MediumnssMageiaMembers the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR...8.8 HighnssMageiaA cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions ...8.8 HighnssMageiaAn attacker could have abused XSLT error handling to associate attacker-controlled content with...6.5 MediumnssMageiaWhen combining CSS properties for overflow and transform, the mouse cursor could interact with...7.5 HighnssMageiaWhen visiting directory listings for `chrome://` URLs as source text, some parameters were...5.3 MediumnssMageiaThe Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of...8.8 HighnssMageiaIn the <code>nsTArray_Impl::ReplaceElementsAt()</code> function, an integer overflow could have...8.8 HighnssMageiaA malicious website that could create a popup could have resized the popup to overlay the address...6.5 MediumnssMageiaIf there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests...4.3 MediumnssMageiaSession history navigations may have led to a use-after-free and potentially exploitable crash....9.8 CriticalnssMageiaAn iframe that was not permitted to run scripts could do so if the user clicked on a <code...8.8 HighnssMageiaIf an object prototype was corrupted by an attacker, they would have been able to set undesired...8.8 HighnssMageiaMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 CriticalnssMageiaAn attacker could have injected CSS into stylesheets accessible via internal URIs, such as...6.5 MediumnssMageiaAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 MediumnssMageiaA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 HighnssMageiaOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 HighnssMageiaWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 MediumnssMageiaA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 CriticalnssMageiaA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 CriticalnssMageiaMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 CriticalnssMageiaFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 MediumnssMageiaWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 MediumnssMageiaRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 MediumnssMageiaAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 MediumnssMageiaDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 HighnssMageiaMozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the...8.8 HighnssMageiaDue to a layout change, iframe contents could have been rendered outside of its border. This...5.4 MediumnssMageiaWhen generating the assembly code for <code>MLoadTypedArrayElementHole</code>, an incorrect...6.5 MediumnssMageiaBy using a link with <code>rel="localization"</code> a use-after-free could have been triggered...6.5 MediumnssMageiaIf a compromised content process sent an unexpected number of WebAuthN Extensions in a Register...8.8 HighnssMageiaAfter a VR Process is destroyed, a reference to it may have been retained and used, leading to a...6.5 MediumnssMageia<code>NSSToken</code> objects were referenced via direct points, and could have been accessed in...6.5 MediumnssMageiaRegular expression denial of service in Rust's regex crate7.5 HighnssMageiaAn unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable...9.6 CriticalnssMageiaRemoving an XSLT parameter during processing could have lead to an exploitable use-after-free. We...8.8 HighnssMageiaIn Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.9.8 CriticalnssMageiaxmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator...9.8 CriticalnssMageiaxmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as...9.8 CriticalnssMageiaMozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighnssMageiaWhen a worker is shutdown, it was possible to cause script to run late in the lifecycle, at a...8.8 High- Show moreLoading…