mozjs68 vulnerabilities (Ubuntu)
1,654 vulnerabilities.
mozjs68UbuntuThe `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing...6.5 Mediummozjs68UbuntuWhen a network error occurred during page load, the prior content could have remained in view...7.5 Highmozjs68UbuntuAn HTTP digest authentication nonce value was generated using `rand()` which could lead to...5.9 Mediummozjs68UbuntuA memory allocation check was missing which would lead to a use-after-free if the allocation...8.6 Highmozjs68UbuntuMultiple WebRTC threads could have claimed a newly connected audio input leading to use-after...9.8 Criticalmozjs68UbuntuMemory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of...8.8 Highmozjs68UbuntuWhen saving a page to PDF, certain font styles could have led to a potential use-after-free crash...8.8 Highmozjs68UbuntuWhen importing resources using Web Workers, error messages would distinguish the difference...5.9 Mediummozjs68UbuntuA bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a...6.1 Mediummozjs68UbuntuIf the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not...4.3 Mediummozjs68UbuntuPDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF8.8 Highmozjs68UbuntuMemory safety bugs present in Firefox 124. Some of these bugs showed evidence of memory...8.1 Highmozjs68UbuntuMemory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug...8.1 Highmozjs68UbuntuThere was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server...3.7 Lowmozjs68UbuntuThe MarkStack assignment operator, part of the JavaScript engine, could access uninitialized...5.3 Mediummozjs68UbuntuIf an AlignedBuffer were assigned to itself, the subsequent self-move could result in an...4.0 Mediummozjs68UbuntuAn out-of-memory condition during object initialization could result in an empty shape list. If...6.2 Mediummozjs68UbuntuOn 32-bit versions there were integer-overflows that led to an out-of-bounds-read that...5.9 Mediummozjs68UbuntuIt was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This...7.5 Highmozjs68UbuntuThe JIT created incorrect code for arguments in certain cases. This led to potential use-after...7.8 Highmozjs68UbuntuA use-after-free could occur during WASM execution if garbage collection ran during the creation...8.8 Highmozjs68UbuntuIn certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds...6.5 Mediummozjs68UbuntuIn some code patterns the JIT incorrectly optimized switch statements and generated code with out...8.8 Highmozjs68UbuntuA use-after-free could result if a JavaScript realm was in the process of being initialized when...7.5 Highmozjs68UbuntuGetBoundName could return the wrong version of an object when JIT optimizations were applied....7.5 Highmozjs68UbuntuAn attacker was able to inject an event handler into a privileged object that would allow...8.4 Highmozjs68UbuntuAn attacker was able to perform an out-of-bounds read or write on a JavaScript object by fooling...9.8 Criticalmozjs68UbuntuTo harden ICU against exploitation, the behavior for out-of-memory conditions was changed to...2.7 Lowmozjs68UbuntuAn attacker could have leveraged the Windows Error Reporter to run arbitrary code on the system...5.9 Mediummozjs68UbuntuMemory safety bugs present in Firefox 123. Some of these bugs showed evidence of memory...9.8 Criticalmozjs68UbuntuMemory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. Some of...8.8 Highmozjs68UbuntuData was not properly sanitized when decoding a QUIC ACK frame; this could have led to...7.5 Highmozjs68UbuntuIf an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have...8.1 Highmozjs68UbuntuA missing delay on when pointer lock was used could have allowed a malicious page to trick a user...5.5 Mediummozjs68UbuntuUsing a markup injection an attacker could have stolen nonce values. This could have been used to...6.1 Mediummozjs68UbuntuThe permission prompt input delay could have expired while the window is not in focus, which made...6.1 Mediummozjs68Ubuntu`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()...8.4 Highmozjs68UbuntuReturn registers were overwritten which could have allowed an attacker to execute arbitrary code....8.1 Highmozjs68UbuntuPassing invalid data could have led to invalid wasm values being created, such as arbitrary...3.7 Lowmozjs68UbuntuMemory safety bugs present in Firefox 122. Some of these bugs showed evidence of memory...8.1 Highmozjs68UbuntuThe incorrect object was checked for NULL in the built-in profiler, potentially leading to...6.5 Mediummozjs68UbuntuWhen opening a website using the `firefox://` protocol handler, SameSite cookies were not...8.3 Highmozjs68UbuntuThe `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not...9.8 Criticalmozjs68UbuntuMemory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. Some of...8.1 Highmozjs68UbuntuIncorrect code generation could have led to unexpected numeric conversions and potential...7.5 Highmozjs68UbuntuSet-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an...6.1 Mediummozjs68UbuntuA malicious website could have used a combination of exiting fullscreen mode and ...6.1 Mediummozjs68UbuntuIf a website set a large custom cursor, portions of the cursor could have overlapped with the...6.1 Mediummozjs68UbuntuA website could have obscured the fullscreen notification by using a dropdown select input...4.3 Mediummozjs68UbuntuThrough a series of API calls and redirects, an attacker-controlled alert dialog could have been...6.5 Medium- Show moreLoading…