mozjs68 vulnerabilities (Ubuntu)
1,654 vulnerabilities.
mozjs68UbuntuA difference in the handling of StructFields and ArrayTypes in WASM could be used to trigger an...9.8 Criticalmozjs68UbuntuThe JavaScript garbage collector could mis-color cross-compartment objects if OOM conditions were...9.8 Criticalmozjs68UbuntuFirefox normally asks for confirmation before asking the operating system to find an application...7.5 Highmozjs68UbuntuInternal browser event interfaces were exposed to web content when privileged EventHandler...8.8 Highmozjs68UbuntuA potentially exploitable type confusion could be triggered when looking up a property name on an...9.8 Criticalmozjs68UbuntuIncorrect garbage collection interaction could have led to a use-after-free. This vulnerability...8.8 Highmozjs68UbuntuCalling `PK11_Encrypt()` in NSS using CKM_CHACHA20 and the same buffer for input and output can...6.5 Mediummozjs68UbuntuThe date picker could partially obscure security prompts. This could be used by a malicious site...6.5 Mediummozjs68UbuntuA select option could partially obscure security prompts. This could be used by a malicious site...8.1 Highmozjs68UbuntuIncorrect garbage collection interaction in IndexedDB could have led to a use-after-free. This...8.8 Highmozjs68UbuntuUnexpected marking work at the start of sweeping could have led to a use-after-free. This...8.8 Highmozjs68UbuntuANGLE failed to initialize parameters which lead to reading from uninitialized memory. This could...6.5 Mediummozjs68UbuntuIt was possible for a web extension with minimal permissions to create a `StreamFilter` which...8.1 Highmozjs68UbuntuFirefox adds web-compatibility shims in place of some tracking scripts blocked by Enhanced...6.1 Mediummozjs68UbuntuEditor code failed to check an attribute value. This could have led to an out-of-bounds read....8.8 Highmozjs68UbuntuIncomplete WebAssembly exception handing could have led to a use-after-free. This vulnerability...8.8 Highmozjs68UbuntuA type confusion bug in WebAssembly could be leveraged by an attacker to potentially achieve code...8.8 Highmozjs68UbuntuInsufficient checks when processing graphics shared memory could have led to memory corruption....9.6 Criticalmozjs68UbuntuSelect options could obscure the fullscreen notification dialog. This could be used by a...6.5 Mediummozjs68UbuntuType Confusion in Async Generators in Javascript Engine7.5 Highmozjs68UbuntuMemory safety bugs fixed in Firefox 128 and Thunderbird 1288.8 Highmozjs68UbuntuIncorrect listing of stack frames4.3 Mediummozjs68UbuntuIncorrect listing of stack frames5.5 Mediummozjs68UbuntuCSP violation leakage when using devtools5.3 Mediummozjs68UbuntuIncorrect handling of SameSite cookies9.8 Criticalmozjs68UbuntuForm validation popups could block exiting full-screen mode4.3 Mediummozjs68UbuntuMemory corruption in NSS8.8 Highmozjs68UbuntuCursor could be moved out of the viewport using pointerlock.4.3 Mediummozjs68UbuntuLeaving pointerlock by pressing the escape key could be prevented8.8 Highmozjs68UbuntuOut-of-bounds read in clipboard component8.2 Highmozjs68UbuntuMemory safety bugs fixed in Firefox 128, Firefox ESR 115.13, Thunderbird 128, and Thunderbird 115.137.5 Highmozjs68UbuntuMemory corruption in thread creation7.4 Highmozjs68UbuntuMemory corruption in NSS9.8 Criticalmozjs68UbuntuRace condition in permission assignment4.7 Mediummozjs68UbuntuMemory safety bugs present in Firefox 126. Some of these bugs showed evidence of memory...9.8 Criticalmozjs68UbuntuIn violation of spec, cookie prefixes such as `__Secure` were being ignored if they were not...9.8 Criticalmozjs68UbuntuBy manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid...6.1 Mediummozjs68UbuntuA website was able to detect when a user took a screenshot of a page using the built-in...4.3 Mediummozjs68UbuntuIf an out-of-memory condition occurs at a specific point using allocations in the probabilistic...9.8 Criticalmozjs68UbuntuAn attacker could have caused a use-after-free in the JavaScript engine to read memory in the...7.5 Highmozjs68UbuntuIn addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay...4.3 Mediummozjs68UbuntuMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 Highmozjs68UbuntuBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 Highmozjs68UbuntuOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 Mediummozjs68UbuntuBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 Mediummozjs68UbuntuBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 Mediummozjs68UbuntuIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 Highmozjs68UbuntuMemory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory...9.8 Criticalmozjs68UbuntuA file dialog shown while in full-screen mode could have resulted in the window remaining...8.2 Highmozjs68UbuntuAn iterator stop condition was missing when handling WASM code in the built-in profiler,...5.9 Medium- Show moreLoading…