mozjs38 vulnerabilities (Ubuntu)
1,842 vulnerabilities.
mozjs38UbuntuInternal browser event interfaces were exposed to web content when privileged EventHandler...8.8 Highmozjs38UbuntuA potentially exploitable type confusion could be triggered when looking up a property name on an...9.8 Criticalmozjs38UbuntuIncorrect garbage collection interaction could have led to a use-after-free. This vulnerability...8.8 Highmozjs38UbuntuCalling `PK11_Encrypt()` in NSS using CKM_CHACHA20 and the same buffer for input and output can...6.5 Mediummozjs38UbuntuThe date picker could partially obscure security prompts. This could be used by a malicious site...6.5 Mediummozjs38UbuntuA select option could partially obscure security prompts. This could be used by a malicious site...8.1 Highmozjs38UbuntuIncorrect garbage collection interaction in IndexedDB could have led to a use-after-free. This...8.8 Highmozjs38UbuntuUnexpected marking work at the start of sweeping could have led to a use-after-free. This...8.8 Highmozjs38UbuntuANGLE failed to initialize parameters which lead to reading from uninitialized memory. This could...6.5 Mediummozjs38UbuntuIt was possible for a web extension with minimal permissions to create a `StreamFilter` which...8.1 Highmozjs38UbuntuFirefox adds web-compatibility shims in place of some tracking scripts blocked by Enhanced...6.1 Mediummozjs38UbuntuEditor code failed to check an attribute value. This could have led to an out-of-bounds read....8.8 Highmozjs38UbuntuIncomplete WebAssembly exception handing could have led to a use-after-free. This vulnerability...8.8 Highmozjs38UbuntuA type confusion bug in WebAssembly could be leveraged by an attacker to potentially achieve code...8.8 Highmozjs38UbuntuInsufficient checks when processing graphics shared memory could have led to memory corruption....9.6 Criticalmozjs38UbuntuSelect options could obscure the fullscreen notification dialog. This could be used by a...6.5 Mediummozjs38UbuntuType Confusion in Async Generators in Javascript Engine7.5 Highmozjs38UbuntuMemory safety bugs fixed in Firefox 128 and Thunderbird 1288.8 Highmozjs38UbuntuIncorrect listing of stack frames4.3 Mediummozjs38UbuntuIncorrect listing of stack frames5.5 Mediummozjs38UbuntuCSP violation leakage when using devtools5.3 Mediummozjs38UbuntuIncorrect handling of SameSite cookies9.8 Criticalmozjs38UbuntuForm validation popups could block exiting full-screen mode4.3 Mediummozjs38UbuntuMemory corruption in NSS8.8 Highmozjs38UbuntuCursor could be moved out of the viewport using pointerlock.4.3 Mediummozjs38UbuntuLeaving pointerlock by pressing the escape key could be prevented8.8 Highmozjs38UbuntuOut-of-bounds read in clipboard component8.2 Highmozjs38UbuntuMemory safety bugs fixed in Firefox 128, Firefox ESR 115.13, Thunderbird 128, and Thunderbird 115.137.5 Highmozjs38UbuntuMemory corruption in thread creation7.4 Highmozjs38UbuntuMemory corruption in NSS9.8 Criticalmozjs38UbuntuRace condition in permission assignment4.7 Mediummozjs38UbuntuMemory safety bugs present in Firefox 126. Some of these bugs showed evidence of memory...9.8 Criticalmozjs38UbuntuIn violation of spec, cookie prefixes such as `__Secure` were being ignored if they were not...9.8 Criticalmozjs38UbuntuBy manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid...6.1 Mediummozjs38UbuntuA website was able to detect when a user took a screenshot of a page using the built-in...4.3 Mediummozjs38UbuntuIf an out-of-memory condition occurs at a specific point using allocations in the probabilistic...9.8 Criticalmozjs38UbuntuAn attacker could have caused a use-after-free in the JavaScript engine to read memory in the...7.5 Highmozjs38UbuntuIn addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay...4.3 Mediummozjs38UbuntuMemory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of...7.0 Highmozjs38UbuntuBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory...8.6 Highmozjs38UbuntuOffscreen Canvas did not properly track cross-origin tainting, which could be used to access...6.1 Mediummozjs38UbuntuBy tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented...4.7 Mediummozjs38UbuntuBy monitoring the time certain operations take, an attacker could have guessed which external...4.3 Mediummozjs38UbuntuIf a garbage collection was triggered at the right time, a use-after-free could have occurred...8.1 Highmozjs38UbuntuMemory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory...9.8 Criticalmozjs38UbuntuA file dialog shown while in full-screen mode could have resulted in the window remaining...8.2 Highmozjs38UbuntuAn iterator stop condition was missing when handling WASM code in the built-in profiler,...5.9 Mediummozjs38UbuntuThe `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing...6.5 Mediummozjs38UbuntuWhen a network error occurred during page load, the prior content could have remained in view...7.5 Highmozjs38UbuntuAn HTTP digest authentication nonce value was generated using `rand()` which could lead to...5.9 Medium- Show moreLoading…