nspr vulnerabilities (Mageia)
403 vulnerabilities.
nsprMageiaThe origin of an external protocol handler prompt could have been obscured using a data: URL...5.3 MediumnsprMageiaAn attacker could have caused a use-after-free when accessibility was enabled, leading to a...7.5 HighnsprMageiaA permission leak could have occurred from a trusted site to an untrusted site via `embed` or ...7.5 HighnsprMageiaMozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the...8.8 HighnsprMageiaConcurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a...6.5 MediumnsprMageiaDuring iframe navigation, certain pages did not have their FeaturePolicy fully initialized...6.5 MediumnsprMageiaBy injecting a cookie with certain special characters, an attacker on a shared subdomain which is...6.5 MediumnsprMageiaWhen injecting an HTML base element, some requests would ignore the CSP's base-uri settings and...6.1 MediumnsprMageiaMembers the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR...8.8 HighnsprMageiaA cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions ...8.8 HighnsprMageiaAn attacker could have abused XSLT error handling to associate attacker-controlled content with...6.5 MediumnsprMageiaMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 CriticalnsprMageiaAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 MediumnsprMageiaA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 HighnsprMageiaOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 HighnsprMageiaWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 MediumnsprMageiaA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 CriticalnsprMageiaA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 CriticalnsprMageiaMozilla developers Calixte Denizet, Kershaw Chang, Christian Holler, Jason Kratzer, Gabriele...8.8 HighnsprMageiaMalicious websites could have confused Firefox into showing the wrong origin when asking to...6.5 MediumnsprMageiaAfter accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the...6.5 MediumnsprMageiaSecuritypolicyviolation events could have leaked cross-origin information for frame-ancestors...6.5 MediumnsprMageiaWhen navigating from inside an iframe while requesting fullscreen access, an attacker-controlled...4.3 MediumnsprMageiaWhen inserting text while in edit mode, some characters might have lead to out-of-bounds memory...6.5 MediumnsprMageiaWhen resizing a popup while requesting fullscreen access, the popup would have become unable to...7.5 HighnsprMageiaCertain network request objects were freed too early when releasing a network request handle....8.8 HighnsprMageiaMalicious websites could have tricked users into accepting launching a program to handle an...6.5 MediumnsprMageiaApplying a CSS filter effect could have accessed out of bounds memory. This could have lead to a...8.8 HighnsprMageiaConstructing audio sinks could have lead to a race condition when playing audio files and closing...7.5 HighnsprMageiaIt was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox....10.0 CriticalnsprMageiaMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighnsprMageiaA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighnsprMageiaOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighnsprMageiaMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighnsprMageiaAn out of date graphics library (Angle) likely contained vulnerabilities that could potentially...9.8 CriticalnsprMageiaMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighnsprMageiaA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumnsprMageiaUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumnsprMageiaA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighnsprMageiaWhen recursing through graphical layers while scrolling, an iterator may have become invalid,...8.8 HighnsprMageiaBy exploiting an Open Redirect vulnerability on a website, an attacker could have spoofed the...6.1 MediumnsprMageiaFirefox sometimes ran the onload handler for SVG elements that the DOM sanitizer decided to...6.1 MediumnsprMageiaMozilla developers reported memory safety bugs present in Firefox 80 and Firefox ESR 78.2. Some...8.8 HighnsprMageiaWhen aborting an operation, such as a fetch, an abort signal may be deleted while alerting the...8.8 HighnsprMageiaBy holding a reference to the eval() function from an about:blank window, a malicious webpage...6.5 MediumnsprMageiaA flaw was found in the way CHACHA20-POLY1305 was implemented in NSS in versions before 3.55....9.1 CriticalnsprMageiaWhen performing EC scalar point multiplication, the wNAF point multiplication algorithm was used;...5.3 MediumnsprMageiaDuring ECDSA signature generation, padding applied in the nonce designed to ensure constant-time...4.7 MediumnsprMageiaWhen converting coordinates from projective to affine, the modular inversion was not performed in...4.7 MediumnsprMageiaMozilla developers and community members reported memory safety bugs present in Firefox 78 and...8.8 High- Show moreLoading…