mozjs68 vulnerabilities (Ubuntu)
1,654 vulnerabilities.
mozjs68UbuntuWhen storing and re-accessing data on a networking channel, the length of buffers may have been...7.5 Highmozjs68UbuntuSome WASM source files could have caused a crash when loaded in devtools. This vulnerability...6.5 Mediummozjs68UbuntuA compromised content process could have updated the document URI. This could have allowed an...4.3 Mediummozjs68UbuntuThe WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have...8.8 Highmozjs68UbuntuIn some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could...7.5 Highmozjs68UbuntuAn unchecked return value in TLS handshake code could have caused a potentially exploitable crash...7.5 Highmozjs68UbuntuMemory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of...8.8 Highmozjs68UbuntuIn specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This...6.5 Mediummozjs68UbuntuA malicious devtools extension could have been used to escalate privileges. This vulnerability...8.8 Highmozjs68UbuntuA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 Highmozjs68UbuntuA phishing site could have repurposed an `about:` dialog to show phishing content with an...4.3 Mediummozjs68UbuntuWhen a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security...6.5 Mediummozjs68UbuntuA Linux user opening the print preview dialog could have caused the browser to crash. This...6.5 Mediummozjs68UbuntuIt was possible for certain browser prompts and dialogs to be activated or dismissed...4.3 Mediummozjs68UbuntuAn out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a...6.5 Mediummozjs68UbuntuMemory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory...8.8 Highmozjs68UbuntuBrowser tab titles were being leaked by GNOME to system logs. This could potentially expose the...6.5 Mediummozjs68UbuntuUnder certain conditions, Firefox did not display a warning when a user attempted to navigate to...4.3 Mediummozjs68UbuntuApplications which spawn a Toast notification in a background thread may have obscured fullscreen...4.3 Mediummozjs68UbuntuA `` element could have been manipulated to paint content outside of a sandboxed iframe. This...6.5 Mediummozjs68UbuntuIn some instances, the user-agent would allow push requests which lacked a valid VAPID even...4.3 Mediummozjs68UbuntuThe timing of a button click causing a popup to disappear was approximately the same length as...6.1 Mediummozjs68UbuntuTypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in...8.8 Highmozjs68Ubuntu`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only...6.5 Mediummozjs68UbuntuMultiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This...4.3 Mediummozjs68UbuntuMemory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5. Some of...8.8 Highmozjs68UbuntuThe `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on...8.8 Highmozjs68UbuntuA use-after-free was identified in the `nsDNSService::Init`. This issue appears to manifest...8.8 Highmozjs68UbuntuThe `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in...8.8 Highmozjs68UbuntuThe `VideoBridge` allowed any content process to use textures produced by remote decoders. This...6.5 Mediummozjs68UbuntuA use-after-free condition affected TLS socket creation when under memory pressure. This...8.8 Highmozjs68UbuntuFirefox was susceptible to a heap buffer overflow in `nsTextFragment` due to insufficient OOM...8.8 Highmozjs68UbuntuWhen resolving a symlink, a race may occur where the buffer passed to `readlink` may actually be...5.3 Mediummozjs68UbuntuThe WebGL `DrawElementsInstanced` method was susceptible to a heap buffer overflow when used on...8.8 Highmozjs68UbuntuMemory safety bugs present in Firefox 119. Some of these bugs showed evidence of memory...8.8 Highmozjs68UbuntuMemory safety bugs present in Firefox 119, Firefox 115.4, and Thunderbird 115.4. Some of these...8.8 Highmozjs68UbuntuIf an attacker needed a user to load an insecure http: page and knew that user had enabled HTTPS...6.5 Mediummozjs68UbuntuWhen an https: web page created a pop-up from a "javascript:" URL, that pop-up was incorrectly...6.5 Mediummozjs68UbuntuRelative URLs starting with three slashes were incorrectly parsed, and a path-traversal "/../"...6.5 Mediummozjs68UbuntuWhen using X11, text selected by the page using the Selection API was erroneously copied into the...8.8 Highmozjs68UbuntuOwnership mismanagement led to a use-after-free in ReadableByteStreams This vulnerability affects...8.8 Highmozjs68UbuntuThe black fade animation when exiting fullscreen is roughly the length of the anti-clickjacking...5.4 Mediummozjs68UbuntuIt was possible to cause the use of a MessagePort after it had already been freed, which could...6.5 Mediummozjs68UbuntuOn some systems—depending on the graphics settings and drivers—it was possible to force an out-of...6.5 Mediummozjs68UbuntuMemory safety bugs present in Firefox 118. Some of these bugs showed evidence of memory...9.8 Criticalmozjs68UbuntuMemory safety bugs present in Firefox 118, Firefox ESR 115.3, and Thunderbird 115.3. Some of...9.8 Criticalmozjs68UbuntuA malicious web site can enter fullscreen mode while simultaneously triggering a WebAuthn prompt....4.3 Mediummozjs68UbuntuDuring garbage collection extra operations were performed on a object that should not be. This...7.5 Highmozjs68UbuntuThe executable file warning was not presented when downloading .msix, .msixbundle, .appx, and ...6.5 Mediummozjs68UbuntuA website could have obscured the full screen notification by using the file open dialog. This...4.3 Medium- Show moreLoading…