mozjs38 vulnerabilities (Ubuntu)
1,842 vulnerabilities.
mozjs38UbuntuThe WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have...8.8 Highmozjs38UbuntuIn some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could...7.5 Highmozjs38UbuntuAn unchecked return value in TLS handshake code could have caused a potentially exploitable crash...7.5 Highmozjs38UbuntuMemory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of...8.8 Highmozjs38UbuntuIn specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This...6.5 Mediummozjs38UbuntuA malicious devtools extension could have been used to escalate privileges. This vulnerability...8.8 Highmozjs38UbuntuA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 Highmozjs38UbuntuA phishing site could have repurposed an `about:` dialog to show phishing content with an...4.3 Mediummozjs38UbuntuWhen a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security...6.5 Mediummozjs38UbuntuA Linux user opening the print preview dialog could have caused the browser to crash. This...6.5 Mediummozjs38UbuntuIt was possible for certain browser prompts and dialogs to be activated or dismissed...4.3 Mediummozjs38UbuntuAn out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a...6.5 Mediummozjs38UbuntuMemory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory...8.8 Highmozjs38UbuntuBrowser tab titles were being leaked by GNOME to system logs. This could potentially expose the...6.5 Mediummozjs38UbuntuUnder certain conditions, Firefox did not display a warning when a user attempted to navigate to...4.3 Mediummozjs38UbuntuApplications which spawn a Toast notification in a background thread may have obscured fullscreen...4.3 Mediummozjs38UbuntuA `` element could have been manipulated to paint content outside of a sandboxed iframe. This...6.5 Mediummozjs38UbuntuIn some instances, the user-agent would allow push requests which lacked a valid VAPID even...4.3 Mediummozjs38UbuntuThe timing of a button click causing a popup to disappear was approximately the same length as...6.1 Mediummozjs38UbuntuTypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in...8.8 Highmozjs38Ubuntu`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only...6.5 Mediummozjs38UbuntuMultiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This...4.3 Mediummozjs38UbuntuMemory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5. Some of...8.8 Highmozjs38UbuntuThe `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on...8.8 Highmozjs38UbuntuA use-after-free was identified in the `nsDNSService::Init`. This issue appears to manifest...8.8 Highmozjs38UbuntuThe `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in...8.8 Highmozjs38UbuntuThe `VideoBridge` allowed any content process to use textures produced by remote decoders. This...6.5 Mediummozjs38UbuntuA use-after-free condition affected TLS socket creation when under memory pressure. This...8.8 Highmozjs38UbuntuFirefox was susceptible to a heap buffer overflow in `nsTextFragment` due to insufficient OOM...8.8 Highmozjs38UbuntuWhen resolving a symlink, a race may occur where the buffer passed to `readlink` may actually be...5.3 Mediummozjs38UbuntuThe WebGL `DrawElementsInstanced` method was susceptible to a heap buffer overflow when used on...8.8 Highmozjs38UbuntuMemory safety bugs present in Firefox 119. Some of these bugs showed evidence of memory...8.8 Highmozjs38UbuntuMemory safety bugs present in Firefox 119, Firefox 115.4, and Thunderbird 115.4. Some of these...8.8 Highmozjs38UbuntuIf an attacker needed a user to load an insecure http: page and knew that user had enabled HTTPS...6.5 Mediummozjs38UbuntuWhen an https: web page created a pop-up from a "javascript:" URL, that pop-up was incorrectly...6.5 Mediummozjs38UbuntuRelative URLs starting with three slashes were incorrectly parsed, and a path-traversal "/../"...6.5 Mediummozjs38UbuntuWhen using X11, text selected by the page using the Selection API was erroneously copied into the...8.8 Highmozjs38UbuntuOwnership mismanagement led to a use-after-free in ReadableByteStreams This vulnerability affects...8.8 Highmozjs38UbuntuThe black fade animation when exiting fullscreen is roughly the length of the anti-clickjacking...5.4 Mediummozjs38UbuntuIt was possible to cause the use of a MessagePort after it had already been freed, which could...6.5 Mediummozjs38UbuntuOn some systems—depending on the graphics settings and drivers—it was possible to force an out-of...6.5 Mediummozjs38UbuntuMemory safety bugs present in Firefox 118. Some of these bugs showed evidence of memory...9.8 Criticalmozjs38UbuntuMemory safety bugs present in Firefox 118, Firefox ESR 115.3, and Thunderbird 115.3. Some of...9.8 Criticalmozjs38UbuntuA malicious web site can enter fullscreen mode while simultaneously triggering a WebAuthn prompt....4.3 Mediummozjs38UbuntuDuring garbage collection extra operations were performed on a object that should not be. This...7.5 Highmozjs38UbuntuThe executable file warning was not presented when downloading .msix, .msixbundle, .appx, and ...6.5 Mediummozjs38UbuntuA website could have obscured the full screen notification by using the file open dialog. This...4.3 Mediummozjs38UbuntuA malicious installed WebExtension could open arbitrary URLs, which under the right circumstance...4.3 Mediummozjs38UbuntuDrivers are not always robust to extremely large draw calls and in some cases this scenario could...7.5 Highmozjs38UbuntuAn attacker with temporary script access to a site could have set a cookie containing invalid...5.3 Medium- Show moreLoading…