Mozilla Firefox for Android

33 published vulnerabilities name this product.

As the CNAs write it in their CVE records (vendor and product); the versions are theirs.

CVEVulnerable versionsTitleSeverityPublishedEPSSExploitation
CVE-2024-8897unspecified – < 130.0.1Under certain conditions, an attacker with the ability to redirect users to a malicious site via an open redirect on a trusted site, may be MEDIUM 6.17.6 %
CVE-2023-29546unspecified – < 112When recording the screen while in Private Browsing on Firefox for Android the address bar and keyboard were not hidden, potentially leakingMEDIUM 6.50.5 %
CVE-2023-29534unspecified – < 112Different techniques existed to obscure the fullscreen notification in Firefox and Focus for Android. These could have led to potential useCRITICAL 9.10.7 %
CVE-2023-25747unspecified – < 110.1.0A potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below version 30. *This bug onlHIGH 7.50.6 %
CVE-2023-29551unspecified – < 112Memory safety bugs present in Firefox 111. Some of these bugs showed evidence of memory corruption and we presume that with enough effort soHIGH 8.80.5 %
CVE-2023-29550unspecified – < 112Memory safety bugs present in Firefox 111 and Firefox ESR 102.9. Some of these bugs showed evidence of memory corruption and we presume thatHIGH 8.80.7 %
CVE-2023-29549unspecified – < 112Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. This may have created a vulnMEDIUM 6.50.3 %
CVE-2023-29548unspecified – < 112A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result. This vulnerability affects Firefox < 112, FoMEDIUM 6.50.7 %
CVE-2023-29547unspecified – < 112When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have sMEDIUM 6.50.5 %
CVE-2023-29544unspecified – < 112If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused memory corruption and aMEDIUM 6.50.5 %
CVE-2023-29543unspecified – < 112An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vectHIGH 8.80.5 %
CVE-2023-29541unspecified – < 112Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled commHIGH 8.80.7 %
CVE-2023-29540unspecified – < 112Using a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to external protocol links in sandboxed iframes witMEDIUM 6.10.3 %
CVE-2023-29539unspecified – < 112When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL chaHIGH 8.80.7 %
CVE-2023-29538unspecified – < 112Under specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-extension:///</code> URMEDIUM 4.30.4 %
CVE-2023-29537unspecified – < 112Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code. This vulnHIGH 7.50.6 %
CVE-2023-29536unspecified – < 112An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertioHIGH 8.80.7 %
CVE-2023-29535unspecified – < 112Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced. This resulted in memory corrupMEDIUM 6.50.7 %
CVE-2023-29533unspecified – < 112A website could have obscured the fullscreen notification by using a combination of <code>window.open</code>, fullscreen requests, <code>winMEDIUM 4.30.6 %
CVE-2022-26486unspecified – < 97.3.0An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We have had reports of attaCRITICAL 9.62.4 %KEV
CVE-2022-26485unspecified – < 97.3.0Removing an XSLT parameter during processing could have lead to an exploitable use-after-free. We have had reports of attacks in the wild abHIGH 8.814 %KEV
CVE-2022-1802unspecified – < 100.3.0If an attacker was able to corrupt the methods of an Array object in JavaScript via prototype pollution, they could have achieved execution HIGH 8.828 %
CVE-2022-1529unspecified – < 100.3.0An attacker could have sent a message to the parent process where the contents were used to double-index into a JavaScript object, leading tHIGH 8.818 %
CVE-2021-29952unspecified – < 88.1.3When Web Render components were destructed, a race condition could have caused undefined behavior, and we presume that with enough effort maHIGH 7.50.7 %
CVE-2021-29953unspecified – < 88.1.3A malicious webpage could have forced a Firefox for Android user into executing attacker-controlled JavaScript in the context of another domMEDIUM 6.10.6 %
CVE-2020-6829unspecified – < 80When performing EC scalar point multiplication, the wNAF point multiplication algorithm was used; which leaked partial information about theMEDIUM 5.31.5 %
CVE-2020-12401unspecified – < 80During ECDSA signature generation, padding applied in the nonce designed to ensure constant-time scalar multiplication was removed, resultinMEDIUM 4.70.3 %
CVE-2020-12400unspecified – < 80When converting coordinates from projective to affine, the modular inversion was not performed in constant time, resulting in a possible timMEDIUM 4.70.3 %
CVE-2020-15664unspecified – < 80By holding a reference to the eval() function from an about:blank window, a malicious webpage could have gained access to the InstallTriggerMEDIUM 6.51.4 %
CVE-2020-15666unspecified – < 80When trying to load a non-video in an audio/video context the exact status code (200, 302, 404, 500, 412, 403, etc.) was disclosed via the MMEDIUM 6.51.2 %
CVE-2020-15668unspecified – < 80A lock was missing when accessing a data structure and importing certificate information into the trust database. This vulnerability affectsMEDIUM 4.30.5 %
CVE-2020-15670unspecified – < 80Mozilla developers reported memory safety bugs present in Firefox for Android 79. Some of these bugs showed evidence of memory corruption anHIGH 8.81.1 %
CVE-2020-15671unspecified – < 80When typing in a password under certain conditions, a race may have occured where the InputContext was not being correctly set for the inputLOW 3.10.5 %