Mozilla Firefox For Android

33 CVEs affecting Mozilla Firefox For Android. Latest disclosed: 2024-09-17. Critical: 0, High: 0.

Top CVEs affecting Mozilla Firefox For Android
CVESeverityScorePublishedSummary
CVE-2024-88972024-09-17Under certain conditions, an attacker with the ability to redirect users to a malicious site via an open redirect on a trusted site, may be able to spoof the a…
CVE-2023-295462023-06-19When recording the screen while in Private Browsing on Firefox for Android the address bar and keyboard were not hidden, potentially leaking sensitive informat…
CVE-2023-295342023-06-19Different techniques existed to obscure the fullscreen notification in Firefox and Focus for Android. These could have led to potential user confusion and spo…
CVE-2023-257472023-06-19A potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below version 30. *This bug only affects Firefox f…
CVE-2023-295512023-06-02Memory 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 h…
CVE-2023-295502023-06-02Memory 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…
CVE-2023-295492023-06-02Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. This may have created a vulnerability relating…
CVE-2023-295482023-06-02A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result. This vulnerability affects Firefox < 112, Focus for Android < 1…
CVE-2023-295472023-06-02When 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. Thi…
CVE-2023-295442023-06-02If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused memory corruption and a potentially exploi…
CVE-2023-295432023-06-02An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vector. This vulnerabil…
CVE-2023-295412023-06-02Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled commands. <br>*This bug…
CVE-2023-295402023-06-02Using a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to external protocol links in sandboxed iframes without <code>allow-to…
CVE-2023-295392023-06-02When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL character. This could…
CVE-2023-295382023-06-02Under specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-extension:///</code> URI during a load req…
CVE-2023-295372023-06-02Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code. This vulnerability affects F…
CVE-2023-295362023-06-02An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruptio…
CVE-2023-295352023-06-02Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced. This resulted in memory corruption and a potentia…
CVE-2023-295332023-06-02A website could have obscured the fullscreen notification by using a combination of <code>window.open</code>, fullscreen requests, <code>window.name</code> ass…
CVE-2022-264862022-12-22An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We have had reports of attacks in the wild abu…