mozjs68 vulnerabilities (Ubuntu)
1,654 vulnerabilities.
mozjs68UbuntuMozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox...9.8 Criticalmozjs68UbuntuUse After Free in Wasmtime6.4 Mediummozjs68UbuntuMozilla developers Bryce Seager van Dyk and the Mozilla Fuzzing Team reported potential...9.8 Criticalmozjs68UbuntuThe Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of...8.8 Highmozjs68UbuntuWhen downloading files on Windows, the % character was not escaped, which could have lead to a...8.8 Highmozjs68UbuntuMozilla developers Gabriele Svelto, Timothy Nikkel, Randell Jesup, Jon Coppeard, and the Mozilla...9.8 Criticalmozjs68UbuntuMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 Criticalmozjs68UbuntuIf array shift operations are not used, the Garbage Collector may have become confused about...4.3 Mediummozjs68UbuntuAn attacker could have injected CSS into stylesheets accessible via internal URIs, such as...6.5 Mediummozjs68UbuntuFirefox's HTML parser did not correctly interpret HTML comment tags, resulting in an incongruity...6.5 Mediummozjs68UbuntuAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 Mediummozjs68UbuntuA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 Highmozjs68UbuntuOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 Highmozjs68UbuntuWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 Mediummozjs68UbuntuA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 Criticalmozjs68UbuntuA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 Criticalmozjs68UbuntuUse after free in Codecs in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to...8.8 Highmozjs68UbuntuMozilla developers Gabriele Svelto, Randell Jesup and the Mozilla Fuzzing Team reported memory...8.8 Highmozjs68UbuntuMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 Criticalmozjs68UbuntuFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 Mediummozjs68UbuntuWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 Mediummozjs68UbuntuRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 Mediummozjs68UbuntuAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 Mediummozjs68UbuntuDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 Highmozjs68UbuntuMozilla developers and community members Randell Jesup, Sebastian Hengst, and the Mozilla Fuzzing...8.8 Highmozjs68UbuntuMozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the...8.8 Highmozjs68UbuntuWhen generating the assembly code for <code>MLoadTypedArrayElementHole</code>, an incorrect...6.5 Mediummozjs68UbuntuUse after free in Wasmtime8.1 Highmozjs68UbuntuMozilla developers Kershaw Chang, Ryan VanderMeulen, and Randell Jesup reported memory safety...8.8 Highmozjs68UbuntuWhen installing an add-on, Firefox verified the signature before prompting the user; but while...7.5 Highmozjs68UbuntuIf an attacker could control the contents of an iframe sandboxed with <code>allow-popups</code>...9.6 Criticalmozjs68UbuntuWhen resizing a popup after requesting fullscreen access, the popup would not display the...4.3 Mediummozjs68UbuntuAn attacker could have caused a use-after-free by forcing a text reflow in an SVG object leading...8.8 Highmozjs68UbuntuCranelift vulnerable to miscompilation of constant values in division on AArch645.9 Mediummozjs68UbuntuMozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 Highmozjs68UbuntuWhen a worker is shutdown, it was possible to cause script to run late in the lifecycle, at a...8.8 Highmozjs68UbuntuWeb-accessible extension pages (pages with a moz-extension:// scheme) were not correctly...8.8 Highmozjs68UbuntuWhen importing resources using Web Workers, error messages would distinguish the difference...6.5 Mediummozjs68UbuntuIf a document created a sandboxed iframe without <code>allow-scripts</code>, and subsequently...9.6 Criticalmozjs68UbuntuIf a user was convinced to drag and drop an image to their desktop or other folder, the resulting...8.8 Highmozjs68UbuntuIf a user installed an extension of a particular type, the extension could have auto-updated...6.5 Mediummozjs68UbuntuMozilla developers and community members Gabriele Svelto, Sebastian Hengst, Randell Jesup, Luan...8.8 Highmozjs68UbuntuImproper Restriction of Operations within the Bounds of a Memory Buffer and Race Condition in crossbeam-utils8.1 Highmozjs68UbuntuA race condition could have allowed bypassing the fullscreen notification which could have lead...5.9 Mediummozjs68UbuntuThe constructed curl command from the "Copy as curl" feature in DevTools was not properly escaped...8.8 Highmozjs68UbuntuMozilla developers Calixte Denizet, Kershaw Chang, Christian Holler, Jason Kratzer, Gabriele...8.8 Highmozjs68UbuntuMalicious websites could have confused Firefox into showing the wrong origin when asking to...6.5 Mediummozjs68UbuntuAfter accepting an untrusted certificate, handling an empty pkcs7 sequence as part of the...6.5 Mediummozjs68UbuntuSecuritypolicyviolation events could have leaked cross-origin information for frame-ancestors...6.5 Mediummozjs68UbuntuWhen navigating from inside an iframe while requesting fullscreen access, an attacker-controlled...4.3 Medium- Show moreLoading…