mozjs38 vulnerabilities (Ubuntu)
1,842 vulnerabilities.
mozjs38UbuntuMalicious websites could have tricked users into accepting launching a program to handle an...6.5 Mediummozjs38UbuntuApplying a CSS filter effect could have accessed out of bounds memory. This could have lead to a...8.8 Highmozjs38UbuntuConstructing audio sinks could have lead to a race condition when playing audio files and closing...7.5 Highmozjs38UbuntuIt was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox....10.0 Criticalmozjs38UbuntuIt was possible to recreate previous cursor spoofing attacks against users with a zoomed native...4.3 Mediummozjs38UbuntuUsing the Location API in a loop could have caused severe application hangs and crashes. This...6.5 Mediummozjs38UbuntuDocuments loaded with the CSP sandbox directive could have escaped the sandbox's script...6.1 Mediummozjs38UbuntuUsing XMLHttpRequest, an attacker could have identified installed applications by probing error...6.5 Mediummozjs38UbuntuWhen invoking protocol handlers for external protocols, a supplied parameter URL containing...6.5 Mediummozjs38UbuntuFailure to correctly record the location of live pointers across wasm instance calls resulted in...8.8 Highmozjs38UbuntuBy misusing a race in our notification code, an attacker could have forcefully hidden the...4.3 Mediummozjs38UbuntuAn incorrect type conversion of sizes from 64bit to 32bit integers allowed an attacker to corrupt...8.8 Highmozjs38UbuntuUnder certain circumstances, asynchronous functions could have caused a navigation to fail but...6.5 Mediummozjs38UbuntuThe executable file warning was not presented when downloading .inetloc files, which, due to a...8.8 Highmozjs38UbuntuMicrosoft introduced a new feature in Windows 10 known as Cloud Clipboard which, if enabled, will...6.5 Mediummozjs38UbuntuDue to an unusual sequence of attacker-controlled events, a Javascript alert() dialog with...4.3 Mediummozjs38UbuntuBy displaying a form validity message in the correct location at the same time as a permission...4.3 Mediummozjs38UbuntuThe Opportunistic Encryption feature of HTTP2 (RFC 8164) allows a connection to be transparently...6.5 Mediummozjs38UbuntuThrough a series of navigations, Firefox could have entered fullscreen mode without notification...4.3 Mediummozjs38UbuntuWhen interacting with an HTML input element's file picker dialog with webkitdirectory set, a use...8.8 Highmozjs38UbuntuThe iframe sandbox rules were not correctly applied to XSLT stylesheets, allowing an iframe to...10.0 Criticalmozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 Highmozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 92. Some of these bugs showed...8.8 Highmozjs38UbuntuDuring process shutdown, a document could have caused a use-after-free of a languages service...7.5 Highmozjs38UbuntuThrough use of reportValidity() and window.open(), a plain-text validation message could have...6.5 Mediummozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 Highmozjs38UbuntuDuring operations on MessageTasks, a task may have been removed while it was still scheduled,...8.8 Highmozjs38UbuntuWhen delegating navigations to the operating system, Firefox would accept the `mk` scheme which...6.5 Mediummozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 91. Some of these bugs showed...8.8 Highmozjs38UbuntuMixed-content checks were unable to analyze opaque origins which led to some mixed content being...6.5 Mediummozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some...8.8 Highmozjs38UbuntuFirefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate...8.1 Highmozjs38UbuntuFirefox for Android could get stuck in fullscreen mode and not exit it even after normal...6.5 Mediummozjs38UbuntuMozilla developers and community members reported memory safety bugs present in Firefox 90. Some...8.8 Highmozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12. Some...8.8 Highmozjs38UbuntuFirefox incorrectly treated an inline list-item element as a block element, resulting in an out...8.8 Highmozjs38UbuntuAfter requesting multiple permissions, and closing the first permission panel, subsequent...6.5 Mediummozjs38UbuntuA suspected race condition when calling getaddrinfo led to memory corruption and a potentially...8.1 Highmozjs38UbuntuA use-after-free vulnerability in media channels could have led to memory corruption and a...8.8 Highmozjs38UbuntuInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 Highmozjs38UbuntuDue to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object,...6.5 Mediummozjs38UbuntuAn issue present in lowering/register allocation could have led to obscure but deterministic...8.8 Highmozjs38UbuntuUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 Highmozjs38UbuntuIf a user had granted a permission to a webpage and saved that grant, any webpage running on the...9.8 Criticalmozjs38UbuntuPassword autofill was enabled without user interaction on insecure websites on Firefox for...8.8 Highmozjs38UbuntuMozilla developers reported memory safety bugs present in Firefox 89. Some of these bugs showed...8.8 Highmozjs38UbuntuThrough a series of DOM manipulations, a message, over which the attacker had control of the text...6.5 Mediummozjs38UbuntuWhen network partitioning was enabled, e.g. as a result of Enhanced Tracking Protection settings,...4.3 Mediummozjs38UbuntuA use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library....8.8 Highmozjs38UbuntuMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 High- Show moreLoading…