mozjs91 vulnerabilities (Ubuntu)
1,429 vulnerabilities.
mozjs91UbuntuMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 Highmozjs91UbuntuWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 Highmozjs91UbuntuAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 Mediummozjs91UbuntuA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 Mediummozjs91UbuntuDocuments were incorrectly assuming an ordering of principal objects when ensuring we were...6.5 Mediummozjs91UbuntuA maliciously crafted favicon could have led to an out of memory crash. This vulnerability...7.5 Highmozjs91UbuntuService workers could reveal script base URL due to dynamic `import()`. This vulnerability...5.3 Mediummozjs91UbuntuA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 Highmozjs91UbuntuAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 Mediummozjs91UbuntuIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 Mediummozjs91UbuntuMozilla developers Randell Jesup, Andrew McCreight, Gabriele Svelto, and the Mozilla Fuzzing Team...8.8 Highmozjs91UbuntuUnder certain circumstances, a call to the <code>bind</code> function may have resulted in the...6.5 Mediummozjs91UbuntuWhen a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain...6.5 Mediummozjs91UbuntuIf multiple instances of resource exhaustion occurred at the incorrect time, the garbage...6.5 Mediummozjs91UbuntuAn attacker could have caused memory corruption and a potentially exploitable use-after-free of a...8.8 Highmozjs91UbuntuUsing a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to...6.1 Mediummozjs91UbuntuUnder specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI...4.3 Mediummozjs91UbuntuMultiple race conditions in the font initialization could have led to memory corruption and...7.5 Highmozjs91UbuntuUse after free in libwebp5.3 Mediummozjs91UbuntuMozilla developers Randell Jesup, Andrew Osmond, Sebastian Hengst, Andrew McCreight, and the...8.8 Highmozjs91UbuntuA wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result....6.5 Mediummozjs91UbuntuSimilar to CVE-2023-28163, this time when choosing 'Save Link As', suggested filenames containing...6.5 Mediummozjs91UbuntuA newline in a filename could have been used to bypass the file extension security mechanisms...9.8 Criticalmozjs91UbuntuFirefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be...8.8 Highmozjs91UbuntuWhen handling the filename directive in the Content-Disposition header, the filename would be...8.8 Highmozjs91UbuntuAn attacker could cause the memory manager to incorrectly free a pointer that addresses attacker...8.8 Highmozjs91UbuntuFollowing a Garbage Collector compaction, weak maps may have been accessed before they were...6.5 Mediummozjs91UbuntuA website could have obscured the fullscreen notification by using a combination of <code>window...4.3 Mediummozjs91UbuntuA local attacker can trick the Mozilla Maintenance Service into applying an unsigned update file...5.5 Mediummozjs91UbuntuAn attacker could have caused an out of bounds memory access using WebGL APIs, leading to memory...9.8 Criticalmozjs91UbuntuMozilla developers and community members Calixte Denizet, Gabriele Svelto, Andrew McCreight, and...8.8 Highmozjs91UbuntuMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 Highmozjs91UbuntuDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 Mediummozjs91UbuntuWhile implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic...8.8 Highmozjs91UbuntuIf temporary "one-time" permissions, such as the ability to use the Camera, were granted to a...8.8 Highmozjs91UbuntuWhen following a redirect to a publicly accessible web extension file, the URL may have been...6.5 Mediummozjs91UbuntuWhen accessing throttled streams, the count of available bytes needed to be checked in the...6.5 Mediummozjs91UbuntuSometimes, when invalidating JIT code while following an iterator, the newly generated code could...6.5 Mediummozjs91UbuntuUnder certain circumstances, a ServiceWorker's offline cache may have leaked to the file system...4.3 Mediummozjs91UbuntuMozilla developers Timothy Nikkel, Gabriele Svelto, Jeff Muizelaar and the Mozilla Fuzzing Team...8.8 Highmozjs91UbuntuMozilla developers Kershaw Chang and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 Highmozjs91UbuntuWhen importing a SPKI RSA public key as ECDSA P-256, the key would be handled incorrectly causing...6.5 Mediummozjs91UbuntuWhen dragging and dropping an image cross-origin, the image's size could potentially be leaked....6.5 Mediummozjs91UbuntuModule load requests that failed were not being checked as to whether or not they were cancelled...8.8 Highmozjs91UbuntuAn invalid downcast from <code>nsTextNode</code> to <code>SVGElement</code> could have lead to...8.8 Highmozjs91UbuntuAn invalid downcast from `nsHTMLDocument` to `nsIContent` could have lead to undefined behavior....9.8 Criticalmozjs91UbuntuCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 Highmozjs91UbuntuThe return value from `gfx::SourceSurfaceSkia::Map()` wasn't being verified which could have...7.5 Highmozjs91UbuntuWhen encoding data from an <code>inputStream</code> in <code>xpcom</code> the size of the input...8.8 Highmozjs91UbuntuDue to URL previews in the network panel of developer tools improperly storing URLs, query...8.8 High- Show moreLoading…