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