mozjs52 vulnerabilities (Ubuntu)
1,829 vulnerabilities.
mozjs52UbuntuA background script invoking <code>requestFullscreen</code> and then blocking the main thread...5.4 Mediummozjs52UbuntuPermission prompts for opening external schemes were only shown for <code>ContentPrincipals</code...8.8 Highmozjs52UbuntuThe <code>Content-Security-Policy-Report-Only</code> header could allow an attacker to leak a...6.5 Mediummozjs52UbuntuAn attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary...8.8 Highmozjs52UbuntuMemory safety bugs fixed in Firefox 1098.8 Highmozjs52UbuntuMemory safety bugs fixed in Firefox 109 and Firefox ESR 102.78.8 Highmozjs52UbuntuCreation of duplicate SystemPrincipal from less secure contexts6.5 Mediummozjs52UbuntuCalls to console.log allowed bypassing Content Security Policy via format directive6.5 Mediummozjs52UbuntuContent Security Policy wasn't being correctly applied to WebSockets in WebWorkers6.5 Mediummozjs52UbuntuURL being dragged from cross-origin iframe into same tab triggers navigation6.5 Mediummozjs52UbuntuMalicious command could be hidden in devtools output on Windows6.5 Mediummozjs52UbuntuArbitrary file read from GTK drag and drop on Linux6.5 Mediummozjs52UbuntuLogic bug in process allocation allowed to read arbitrary files6.5 Mediummozjs52UbuntuMozilla developers and community members Lukas Bernhard, Gabriele Svelto, Randell Jesup, and the...8.8 Highmozjs52UbuntuBy confusing the browser, the fullscreen notification could have been delayed or suppressed,...4.3 Mediummozjs52UbuntuBecause Firefox did not implement the <code>unsafe-hashes</code> CSP directive, an attacker who...8.8 Highmozjs52UbuntuAn out of date library (libusrsctp) contained vulnerabilities that could potentially be exploited...8.8 Highmozjs52UbuntuMozilla developers Randell Jesup, Valentin Gosu, Olli Pettay, and the Mozilla Fuzzing Team...8.8 Highmozjs52UbuntuA file with a long filename could have had its filename truncated to remove the valid extension,...8.8 Highmozjs52UbuntuAn attacker who compromised a content process could have partially escaped the sandbox to read...8.6 Highmozjs52UbuntuMozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in...8.8 Highmozjs52UbuntuUse tables inside of an iframe, an attacker could have caused iframe contents to be rendered...6.5 Mediummozjs52UbuntuIf the user added a security exception for an invalid TLS certificate, opened an ongoing TLS...6.5 Mediummozjs52UbuntuIf a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have...6.1 Mediummozjs52UbuntuService Workers did not detect Private Browsing Mode correctly in all cases, which could have led...4.3 Mediummozjs52UbuntuKeyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread...6.5 Mediummozjs52UbuntuWhen downloading an HTML file, if the title of the page was formatted as a filename with a...7.8 Highmozjs52UbuntuUsing the <code>S.browser_fallback_url parameter</code> parameter, an attacker could redirect a...6.1 Mediummozjs52UbuntuWhen resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be...8.8 Highmozjs52UbuntuCross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing...6.1 Mediummozjs52UbuntuWhen a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the...6.5 Mediummozjs52UbuntuThe garbage collector could have been aborted in several states and zones and <code>GCRuntime:...8.8 Highmozjs52UbuntuThrough a series of popups that reuse windowName, an attacker can cause a window to go fullscreen...6.5 Mediummozjs52UbuntuIf an attacker loaded a font using <code>FontFace()</code> on a background worker, a use-after...7.5 Highmozjs52UbuntuIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may...9.8 Criticalmozjs52UbuntuFreeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have...6.5 Mediummozjs52UbuntuThrough a series of popup and <code>window.print()</code> calls, an attacker can cause a window...6.5 Mediummozjs52UbuntuService Workers should not be able to infer information about opaque cross-origin responses; but...6.5 Mediummozjs52Ubuntuwasmtime_trap_code C API function has out of bounds write vulnerability3.8 Lowmozjs52UbuntuWasmtime vulnerable to data leakage between instances in the pooling allocator8.6 Highmozjs52UbuntuWasmtime vulnerable to out of bounds read/write with zero-memory-pages configuration5.9 Mediummozjs52UbuntuMozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 Highmozjs52UbuntuCertain types of allocations were missing annotations that, if the Garbage Collector was in a...8.8 Highmozjs52UbuntuPrototype pollution vulnerability in beautify-web js-beautify 1.13.7 via the name variable in...9.8 Criticalmozjs52UbuntuInconsistent data in instruction and data cache when creating wasm code could lead to a...6.5 Mediummozjs52UbuntuMozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the...8.8 Highmozjs52UbuntuMembers the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR...8.8 Highmozjs52UbuntuMozilla developer Nika Layzell and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 Highmozjs52UbuntuAn attacker could have written a value to the first element in a zero-length JavaScript array....6.5 Mediummozjs52UbuntuMozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox...8.8 High- Show moreLoading…