nss vulnerabilities (Mageia)
1,368 vulnerabilities.
nssMageiaWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 HighnssMageiaAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 MediumnssMageiaA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 MediumnssMageiaA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 HighnssMageiaAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 MediumnssMageiaIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 MediumnssMageiaMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 HighnssMageiaDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 MediumnssMageiaWhile implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic...8.8 HighnssMageiaWhen accessing throttled streams, the count of available bytes needed to be checked in the...6.5 MediumnssMageiaSometimes, when invalidating JIT code while following an iterator, the newly generated code could...6.5 MediumnssMageiaMozilla developers Philipp and Gabriele Svelto reported memory safety bugs present in Firefox ESR...8.8 HighnssMageiaMozilla developers Kershaw Chang and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighnssMageiaWhen importing a SPKI RSA public key as ECDSA P-256, the key would be handled incorrectly causing...6.5 MediumnssMageiaModule load requests that failed were not being checked as to whether or not they were cancelled...8.8 HighnssMageiaAn invalid downcast from <code>nsTextNode</code> to <code>SVGElement</code> could have lead to...8.8 HighnssMageiaCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighnssMageiaWhen encoding data from an <code>inputStream</code> in <code>xpcom</code> the size of the input...8.8 HighnssMageiaA background script invoking <code>requestFullscreen</code> and then blocking the main thread...5.4 MediumnssMageiaPermission prompts for opening external schemes were only shown for <code>ContentPrincipals</code...8.8 HighnssMageiaThe <code>Content-Security-Policy-Report-Only</code> header could allow an attacker to leak a...6.5 MediumnssMageiaAn attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary...8.8 HighnssMageiaMemory safety bugs fixed in Firefox 109 and Firefox ESR 102.78.8 HighnssMageiaCalls to console.log allowed bypassing Content Security Policy via format directive6.5 MediumnssMageiaContent Security Policy wasn't being correctly applied to WebSockets in WebWorkers6.5 MediumnssMageiaURL being dragged from cross-origin iframe into same tab triggers navigation6.5 MediumnssMageiaArbitrary file read from GTK drag and drop on Linux6.5 MediumnssMageiaBy confusing the browser, the fullscreen notification could have been delayed or suppressed,...4.3 MediumnssMageiaAn out of date library (libusrsctp) contained vulnerabilities that could potentially be exploited...8.8 HighnssMageiaA use-after-free in WebGL extensions could have led to a potentially exploitable crash. This...9.8 CriticalnssMageiaAn optimization in WebGL was incorrect in some cases, and could have led to memory corruption and...8.8 HighnssMageiaA missing check related to tex units could have led to a use-after-free and potentially...6.5 MediumnssMageiaMozilla developers Randell Jesup, Valentin Gosu, Olli Pettay, and the Mozilla Fuzzing Team...8.8 HighnssMageiaA file with a long filename could have had its filename truncated to remove the valid extension,...8.8 HighnssMageiaAn attacker who compromised a content process could have partially escaped the sandbox to read...8.6 HighnssMageiaMozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in...8.8 HighnssMageiaUse tables inside of an iframe, an attacker could have caused iframe contents to be rendered...6.5 MediumnssMageiaIf a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have...6.1 MediumnssMageiaKeyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread...6.5 MediumnssMageiaWhen resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be...8.8 HighnssMageiaCross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing...6.1 MediumnssMageiaWhen a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the...6.5 MediumnssMageiaThe garbage collector could have been aborted in several states and zones and <code>GCRuntime:...8.8 HighnssMageiaThrough a series of popups that reuse windowName, an attacker can cause a window to go fullscreen...6.5 MediumnssMageiaIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may...9.8 CriticalnssMageiaFreeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have...6.5 MediumnssMageiaThrough a series of popup and <code>window.print()</code> calls, an attacker can cause a window...6.5 MediumnssMageiaService Workers should not be able to infer information about opaque cross-origin responses; but...6.5 MediumnssMageiaIn libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared...7.5 HighnssMageiaMozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 High- Show moreLoading…