CVE-2023-37205UnratedThe use of RTL Arabic characters in the address bar may have allowed for URL spoofing. This vulnerability affects Firefox < 115.0.5%
CVE-2023-37204UnratedA website could have obscured the fullscreen notification by using an option element by introducing lag via an expensive computational function. This could have led to user confusion and possible spoo0.5%
CVE-2023-37203High 7.8Insufficient validation in the Drag and Drop API in conjunction with social engineering, may have allowed an attacker to trick end-users into creating a shortcut to local system files. This could hav0.3%
CVE-2023-3482UnratedWhen Firefox is configured to block storage of all cookies, it was still possible to store data in localstorage by using an iframe with a source of 'about:blank'. This could have led to malicious webs0.6%
CVE-2023-37211UnratedMemory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these coul0.8%
CVE-2023-37208UnratedWhen opening Diagcab files, Firefox did not warn the user that these files may contain malicious code. This vulnerability affects Firefox < 115, Firefox ESR < 102.13, and Thunderbird < 102.13.0.2%
CVE-2023-37207UnratedA website could have obscured the fullscreen notification by using a URL with a scheme handled by an external program, such as a mailto URL. This could have led to user confusion and possible spoofing0.7%
CVE-2023-37202UnratedCross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in the main compartment resulting in a use-after-free. This vulnerability affects Fi0.8%
CVE-2023-37201UnratedAn attacker could have triggered a use-after-free condition when creating a WebRTC connection over HTTPS. This vulnerability affects Firefox < 115, Firefox ESR < 102.13, and Thunderbird < 102.13.0.8%
CVE-2023-34417Critical 9.8Memory safety bugs present in Firefox 113. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.0.8%
CVE-2023-34415UnratedWhen choosing a site-isolated process for a document loaded from a data: URL that was the result of a redirect, Firefox would load that document in the same process as the site that issued the redirec0.4%
CVE-2023-25736Critical 9.8An invalid downcast from `nsHTMLDocument` to `nsIContent` could have lead to undefined behavior. This vulnerability affects Firefox < 110.0.7%
CVE-2023-25733High 7.5The return value from `gfx::SourceSurfaceSkia::Map()` wasn't being verified which could have potentially lead to a null pointer dereference. This vulnerability affects Firefox < 110.0.6%
CVE-2023-34416UnratedMemory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these coul0.9%
CVE-2023-34414UnratedThe error page for sites with invalid TLS certificates was missing the
activation-delay Firefox uses to protect prompts and permission dialogs
from attacks that exploit human response time delays. If 0.9%
CVE-2023-29545Medium 6.5Similar to CVE-2023-28163, this time when choosing 'Save Link As', suggested filenames containing environment variable names would have resolved those in the context of the current user.
*This bug o0.6%
CVE-2023-29542Critical 9.8A newline in a filename could have been used to bypass the file extension security mechanisms that replace malicious file extensions such as .lnk with .download. This could have led to accidental exe0.9%
CVE-2023-29532Medium 5.5A local attacker can trick the Mozilla Maintenance Service into applying an unsigned update file by pointing the service at an update file on a malicious SMB server. The update file can be replaced af0.2%
CVE-2023-29531Critical 9.8An attacker could have caused an out of bounds memory access using WebGL APIs, leading to memory corruption and a potentially exploitable crash.
*This bug only affects Firefox and Thunderbird for mac1.0%
CVE-2023-32216UnratedMozilla developers and community members Ronald Crane, Andrew McCreight, Randell Jesup and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 112. Some of these bugs showed eviden0.8%
CVE-2023-32214UnratedProtocol handlers `ms-cxh` and `ms-cxh-full` could have been leveraged to trigger a denial of service.
*Note: This attack only affects Windows. Other operating systems are not affected.* This vulnerab0.9%
CVE-2023-32210UnratedDocuments were incorrectly assuming an ordering of principal objects when ensuring we were loading an appropriately privileged principal. In certain circumstances it might have been possible to cause 0.5%
CVE-2023-32209UnratedA maliciously crafted favicon could have led to an out of memory crash. This vulnerability affects Firefox < 113.0.8%
CVE-2023-32208UnratedService workers could reveal script base URL due to dynamic `import()`. This vulnerability affects Firefox < 113.0.5%
CVE-2023-29550High 8.8Memory safety bugs present in Firefox 111 and Firefox ESR 102.9. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited 0.7%
CVE-2023-29543High 8.8An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vector. This vulnerability affects Firefox for Android < 112, Fi0.5%
CVE-2023-25729High 8.8Permission prompts for opening external schemes were only shown for <code>ContentPrincipals</code> resulting in extensions being able to open them without user interaction via <code>ExpandedPrincipals0.7%
CVE-2023-29537UnratedMultiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code. This vulnerability affects Firefox for Android < 112, Firefox < 112, 0.6%
CVE-2023-29551High 8.8Memory safety bugs present in Firefox 111. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.0.5%
CVE-2023-25739High 8.8Module load requests that failed were not being checked as to whether or not they were cancelled causing a use-after-free in <code>ScriptLoadContext</code>. This vulnerability affects Firefox < 110, T0.7%
CVE-2023-25751UnratedSometimes, when invalidating JIT code while following an iterator, the newly generated code could be overwritten incorrectly. This could lead to a potentially exploitable crash. This vulnerability aff0.7%
CVE-2023-29539UnratedWhen handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL character. This could have led to reflected file download attac0.7%
CVE-2023-25735High 8.8Cross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in the main compartment resulting in a use-after-free after unwrapping the proxy. Th0.7%
CVE-2023-25748Medium 4.3By displaying a prompt with a long description, the fullscreen notification could have been hidden, resulting in potential user confusion or spoofing attacks. <br>*This bug only affects Firefox for An0.3%
CVE-2023-25745High 8.8Memory safety bugs present in Firefox 109. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.0.7%
CVE-2023-29547Medium 6.5When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have silently failed. This could have led to a desynchronization i0.5%
CVE-2023-29549Medium 6.5Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. This may have created a vulnerability relating to JavaScript-implemented sandboxes such 0.3%
CVE-2023-29536UnratedAn attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruption, or a potentially exploitable crash. Th0.7%
CVE-2023-23601UnratedURL being dragged from cross-origin iframe into same tab triggers navigation0.3%
CVE-2023-23603Medium 6.5Calls to console.log allowed bypassing Content Security Policy via format directive0.6%
CVE-2023-23604Medium 6.5Creation of duplicate SystemPrincipal from less secure contexts0.5%
CVE-2023-23605High 8.8Memory safety bugs fixed in Firefox 109 and Firefox ESR 102.70.7%
CVE-2023-23597UnratedLogic bug in process allocation allowed to read arbitrary files0.3%
CVE-2023-29538UnratedUnder specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-extension:///</code> URI during a load request. This leaked directory paths on the 0.4%
CVE-2023-23602Medium 6.5Content Security Policy wasn't being correctly applied to WebSockets in WebWorkers0.6%
CVE-2023-23600UnratedNotification permissions persisted between Normal and Private Browsing on Android0.5%
CVE-2023-29541High 8.8Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled commands. <br>*This bug only affects Firefox for Linux on certai0.7%
CVE-2023-23606High 8.8Memory safety bugs fixed in Firefox 1090.5%
CVE-2023-23598UnratedArbitrary file read from GTK drag and drop on Linux0.6%
CVE-2023-23599UnratedMalicious command could be hidden in devtools output on Windows0.6%