nss vulnerabilities (Mageia)
1,368 vulnerabilities.
nssMageiaAn out of date graphics library (Angle) likely contained vulnerabilities that could potentially...9.8 CriticalnssMageiaMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighnssMageiaA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumnssMageiaUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumnssMageiaA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighnssMageiaMozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some...8.8 HighnssMageiaWhen trying to load a cross-origin resource in an audio/video context a decoding error may have...6.5 MediumnssMageiaAs specified in the W3C Content Security Policy draft, when creating a violation report, "User...4.3 MediumnssMageiaIf Content Security Policy blocked frame navigation, the full destination of a redirect served in...4.3 MediumnssMageiaMozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some...8.8 HighnssMageiaFurther techniques that built on the slipstream research combined with a malicious webpage could...7.4 HighnssMageiaPerforming garbage collection on re-declared JavaScript variables resulted in a user-after-poison...8.8 HighnssMageiaUsing the new logical assignment operators in a JavaScript switch statement could have caused a...8.8 HighnssMageiaIf a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking...4.3 MediumnssMageiaUse after free in WebRTC in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to...8.8 HighnssMageiaMozilla developers reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. Some...8.8 HighnssMageiaWhen an extension with the proxy permission registered to receive <all_urls>, the proxy.onRequest...4.3 MediumnssMageiaUsing techniques that built on the slipstream research, a malicious webpage could have exposed...6.1 MediumnssMageiaWhen a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the...6.5 MediumnssMageiaWhen flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been...8.8 HighnssMageiaCertain input to the CSS Sanitizer confused it, resulting in incorrect components being removed....8.8 HighnssMageiaCertain blit values provided by the user were not properly constrained leading to a heap buffer...8.8 HighnssMageiaUninitialized Use in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to...6.5 MediumnssMageiaMozilla developers reported memory safety bugs present in Firefox 82 and Firefox ESR 78.4. Some...8.8 HighnssMageiaSome websites have a feature "Show Password" where clicking a button will change a password field...6.5 MediumnssMageiaWhen DNS over HTTPS is in use, it intentionally filters RFC1918 and related IP ranges from the...6.5 MediumnssMageiaIf the Compact() method was called on an nsTArray, the array could have been reallocated without...8.8 HighnssMageiaDuring browser shutdown, reference decrementing could have occured on a previously freed object,...8.8 HighnssMageiaFirefox did not block execution of scripts with incorrect MIME types when the response was...6.1 MediumnssMageiaIn some cases, removing HTML elements during sanitization would keep existing SVG event handlers...6.1 MediumnssMageiaIt was possible to cause the browser to enter fullscreen mode without displaying the security UI;...4.3 MediumnssMageiaA parsing and event loading mismatch in Firefox's SVG code could have allowed load events to fire...6.1 MediumnssMageiaSide-channel information leakage in graphics in Google Chrome prior to 87.0.4280.66 allowed a...4.3 MediumnssMageiaMozilla developers and community members reported memory safety bugs present in Firefox 81 and...9.8 CriticalnssMageiaA flaw was found in the way NSS handled CCS (ChangeCipherSpec) messages in TLS 1.3. This flaw...7.5 HighnssMageiaUse after free in WebRTC in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to...8.8 HighnssMageiaWhen recursing through graphical layers while scrolling, an iterator may have become invalid,...8.8 HighnssMageiaBy exploiting an Open Redirect vulnerability on a website, an attacker could have spoofed the...6.1 MediumnssMageiaFirefox sometimes ran the onload handler for SVG elements that the DOM sanitizer decided to...6.1 MediumnssMageiaMozilla developers reported memory safety bugs present in Firefox 80 and Firefox ESR 78.2. Some...8.8 HighnssMageiaA flaw was found in the way CHACHA20-POLY1305 was implemented in NSS in versions before 3.55....9.1 CriticalnssMageiaWhen performing EC scalar point multiplication, the wNAF point multiplication algorithm was used;...5.3 MediumnssMageiaDuring ECDSA signature generation, padding applied in the nonce designed to ensure constant-time...4.7 MediumnssMageiaWhen converting coordinates from projective to affine, the modular inversion was not performed in...4.7 MediumnssMageiaMozilla developers and community members reported memory safety bugs present in Firefox 78 and...8.8 HighnssMageiaBy observing the stack trace for JavaScript errors in web workers, it was possible to leak the...6.5 MediumnssMageiaInappropriate implementation in WebRTC in Google Chrome prior to 84.0.4147.89 allowed an attacker...6.5 MediumnssMageiaWhen performing add-on updates, certificate chains terminating in non-built-in-roots were...6.5 MediumnssMageiaWhen trying to connect to a STUN server, a race condition could have caused a use-after-free of a...8.8 HighnssMageiaWhen processing callbacks that occurred during window flushing in the parent process, the...8.8 High- Show moreLoading…