mozjs38 vulnerabilities (Ubuntu)
1,842 vulnerabilities.
mozjs38UbuntuUsing iterative requests an attacker was able to learn the size of an opaque response, as well as...5.3 Mediummozjs38UbuntuIt was possible for certain browser prompts and dialogs to be activated or dismissed...4.3 Mediummozjs38UbuntuNSS was susceptible to a timing side-channel attack when performing RSA decryption. This attack...6.5 Mediummozjs38UbuntuVP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding.7.5 Highmozjs38UbuntuElectron affected by libvpx's heap buffer overflow in vp8 encoding8.8 Highmozjs38UbuntuDuring process shutdown, it was possible that an `ImageBitmap` was created that would later be...9.8 Criticalmozjs38UbuntuIn a non-standard configuration of Firefox, an integer overflow could have occurred based on...7.5 Highmozjs38UbuntuA hashtable in the Ion Engine could have been mutated while there was a live interior reference,...9.8 Criticalmozjs38UbuntuIn canvas rendering, a compromised content process could have caused a surface to change...7.4 Highmozjs38UbuntuMemory safety bugs present in Firefox 117, Firefox ESR 115.2, and Thunderbird 115.2. Some of...9.8 Criticalmozjs38UbuntuIf Windows failed to duplicate a handle during process creation, the sandbox code may have...9.8 Criticalmozjs38UbuntuDuring Ion compilation, a Garbage Collection could have resulted in a use-after-free condition,...6.5 Mediummozjs38UbuntuA compromised content process could have provided malicious data in a `PathRecording` resulting...6.5 Mediummozjs38UbuntuA compromised content process could have provided malicious data to `FilterNodeD2D1` resulting in...9.8 Criticalmozjs38UbuntuInteger Overflow in RecordedSourceSurfaceCreation8.6 Highmozjs38UbuntuMemory safety bugs fixed in Firefox 117, Firefox ESR 115.2, and Thunderbird 115.28.8 Highmozjs38UbuntuMemory safety bugs fixed in Firefox 117, Firefox ESR 102.15, Firefox ESR 115.2, Thunderbird 102.15, and Thunderbird 115.28.8 Highmozjs38UbuntuBrowsing Context potentially not cleared when closing Private Window7.5 Highmozjs38UbuntuXLL file extensions were downloadable without warnings4.3 Mediummozjs38UbuntuPush notifications saved to disk unencrypted6.5 Mediummozjs38UbuntuPersisted search terms were formatted as URLs3.1 Lowmozjs38UbuntuError reporting methods in SpiderMonkey could have triggered an Out of Memory Exception6.5 Mediummozjs38UbuntuMemory corruption in JIT UpdateRegExpStatics6.5 Mediummozjs38UbuntuMemory corruption in IPC FilePickerShownCallback6.5 Mediummozjs38UbuntuMemory corruption in IPC ColorPickerShownCallback6.5 Mediummozjs38UbuntuMemory corruption in IPC CanvasTranslator6.5 Mediummozjs38UbuntuA potential use-after-free vulnerability existed in SVG Images if the Refresh Driver was...8.8 Highmozjs38UbuntuMemory safety bugs present in Firefox 115. Some of these bugs showed evidence of memory...9.8 Criticalmozjs38UbuntuMemory safety bugs present in Firefox 115, Firefox ESR 115.0, and Thunderbird 115.0. Some of...9.8 Criticalmozjs38UbuntuMemory safety bugs present in Firefox 115, Firefox ESR 115.0, Firefox ESR 102.13, Thunderbird 115...9.8 Criticalmozjs38UbuntuWhen the number of cookies per domain was exceeded in `document.cookie`, the actual cookie jar...7.5 Highmozjs38UbuntuWhen opening appref-ms files, Firefox did not warn the user that these files may contain...5.5 Mediummozjs38UbuntuThe Firefox updater created a directory writable by non-privileged users. When uninstalling...6.5 Mediummozjs38UbuntuFull screen notification obscured by external program6.5 Mediummozjs38UbuntuFull screen notification obscured by file open dialog7.5 Highmozjs38UbuntuIn some cases, an untrusted input stream was copied to a stack buffer without checking its size....7.5 Highmozjs38UbuntuRace conditions in reference counting code were found through code inspection. These could have...5.9 Mediummozjs38UbuntuAn out-of-bounds read could have led to an exploitable crash when parsing HTML with DOMParser in...7.5 Highmozjs38UbuntuA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 Highmozjs38UbuntuIn some circumstances, a stale value could have been used for a global variable in WASM JIT...5.3 Mediummozjs38UbuntuOffscreen Canvas did not properly track cross-origin tainting, which could have been used to...5.3 Mediummozjs38UbuntuMemory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. Some of...8.8 Highmozjs38UbuntuCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 Highmozjs38UbuntuWhen recording the screen while in Private Browsing on Firefox for Android the address bar and...6.5 Mediummozjs38UbuntuDifferent techniques existed to obscure the fullscreen notification in Firefox and Focus for...9.1 Criticalmozjs38UbuntuMemory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of...9.8 Criticalmozjs38UbuntuMemory safety bugs present in Firefox 112. Some of these bugs showed evidence of memory...9.8 Criticalmozjs38UbuntuMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 Highmozjs38UbuntuWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 Highmozjs38UbuntuAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 Medium- Show moreLoading…