nss vulnerabilities (Mageia)
1,368 vulnerabilities.
nssMageiaWeb-accessible extension pages (pages with a moz-extension:// scheme) were not correctly...8.8 HighnssMageiaWhen importing resources using Web Workers, error messages would distinguish the difference...6.5 MediumnssMageiaIf a document created a sandboxed iframe without <code>allow-scripts</code>, and subsequently...9.6 CriticalnssMageiaIf a user was convinced to drag and drop an image to their desktop or other folder, the resulting...8.8 HighnssMageiaIf a user installed an extension of a particular type, the extension could have auto-updated...6.5 MediumnssMageiaMozilla developers Calixte Denizet, Kershaw Chang, Christian Holler, Jason Kratzer, Gabriele...8.8 HighnssMageiaMalicious websites could have confused Firefox into showing the wrong origin when asking to...6.5 MediumnssMageiaAfter accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the...6.5 MediumnssMageiaSecuritypolicyviolation events could have leaked cross-origin information for frame-ancestors...6.5 MediumnssMageiaWhen navigating from inside an iframe while requesting fullscreen access, an attacker-controlled...4.3 MediumnssMageiaWhen inserting text while in edit mode, some characters might have lead to out-of-bounds memory...6.5 MediumnssMageiaWhen resizing a popup while requesting fullscreen access, the popup would have become unable to...7.5 HighnssMageiaCertain network request objects were freed too early when releasing a network request handle....8.8 HighnssMageiaMalicious websites could have tricked users into accepting launching a program to handle an...6.5 MediumnssMageiaApplying a CSS filter effect could have accessed out of bounds memory. This could have lead to a...8.8 HighnssMageiaConstructing audio sinks could have lead to a race condition when playing audio files and closing...7.5 HighnssMageiaIt was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox....10.0 CriticalnssMageiaNSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap...9.8 CriticalnssMageiaA use-after-free could have occured when an HTTP2 session object was released on a different...8.8 HighnssMageiaMozilla developers and community members reported memory safety bugs present in Firefox 93 and...8.8 HighnssMageiaDue to an unusual sequence of attacker-controlled events, a Javascript alert() dialog with...4.3 MediumnssMageiaBy displaying a form validity message in the correct location at the same time as a permission...4.3 MediumnssMageiaThe Opportunistic Encryption feature of HTTP2 (RFC 8164) allows a connection to be transparently...6.5 MediumnssMageiaThrough a series of navigations, Firefox could have entered fullscreen mode without notification...4.3 MediumnssMageiaWhen interacting with an HTML input element's file picker dialog with webkitdirectory set, a use...8.8 HighnssMageiaThe iframe sandbox rules were not correctly applied to XSLT stylesheets, allowing an iframe to...10.0 CriticalnssMageiaMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighnssMageiaDuring process shutdown, a document could have caused a use-after-free of a languages service...7.5 HighnssMageiaThrough use of reportValidity() and window.open(), a plain-text validation message could have...6.5 MediumnssMageiaMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighnssMageiaDuring operations on MessageTasks, a task may have been removed while it was still scheduled,...8.8 HighnssMageiaMozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some...8.8 HighnssMageiaMozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12. Some...8.8 HighnssMageiaFirefox incorrectly treated an inline list-item element as a block element, resulting in an out...8.8 HighnssMageiaA suspected race condition when calling getaddrinfo led to memory corruption and a potentially...8.1 HighnssMageiaA use-after-free vulnerability in media channels could have led to memory corruption and a...8.8 HighnssMageiaInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 HighnssMageiaUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 HighnssMageiaData race in crossbeam-deque9.8 CriticalnssMageiaMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighnssMageiaA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighnssMageiaOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighnssMageiaMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighnssMageiaPorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 HighnssMageiaThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 MediumnssMageiaWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 HighnssMageiaIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 HighnssMageiaThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 MediumnssMageiaWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 HighnssMageiaA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 High- Show moreLoading…