Mozilla CVEs
2,561 CVEs and advisories name Mozilla as an affected vendor, 9 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2023-32208Service workers could reveal script base URL due to dynamic `import()`.
- CVE-2023-32215Mozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough, Sebastian Hengst, Andrew McCreight and the Mozilla
- CVE-2023-32213When reading a file, an uninitialized value could have been used as read limit.
- CVE-2023-32212An attacker could have positioned a `datalist` element to obscure the address bar.
- CVE-2023-32211A type checking bug would have led to invalid code being compiled.
- CVE-2023-32207A missing delay in popup notifications could have made it possible for an attacker to trick a user into granting permissions.
- CVE-2023-32206An out-of-bound read could have led to a crash in the RLBox Expat driver.
- CVE-2023-32205In multiple cases browser prompts could have been obscured by popups controlled by content.
- CVE-2023-29551Memory safety bugs present in Firefox 111.
- CVE-2023-29550Memory safety bugs present in Firefox 111 and Firefox ESR 102.9.
- CVE-2023-29549Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm.
- CVE-2023-29548A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result.
- CVE-2023-29547When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have s
- CVE-2023-29544If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused memory corruption and a
- CVE-2023-29543An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vect
- CVE-2023-29541Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled comm
- CVE-2023-29540Using a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to external protocol links in sandboxed iframes wit
- CVE-2023-29539When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL cha
- CVE-2023-29538Under specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-extension:///</code> UR
- CVE-2023-29537Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code.
- CVE-2023-29536An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertio
- CVE-2023-29535Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced.
- CVE-2023-29533A website could have obscured the fullscreen notification by using a combination of <code>window.open</code>, fullscreen requests, <code>win
- CVE-2023-28177Memory safety bugs present in Firefox 110.
- CVE-2023-28176Memory safety bugs present in Firefox 110 and Firefox ESR 102.8.
- CVE-2023-28164Dragging a URL from a cross-origin iframe that was removed during the drag could have led to user confusion and website spoofing attacks.
- CVE-2023-28163When downloading files through the Save As dialog on Windows with suggested filenames containing environment variable names, Windows would h
- CVE-2023-28162While implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic type.
- CVE-2023-28161If temporary "one-time" permissions, such as the ability to use the Camera, were granted to a document loaded using a file: URL, that permis
- CVE-2023-28160When following a redirect to a publicly accessible web extension file, the URL may have been translated to the actual local path, leaking po