Vendor
Mozilla
2,559 known vulnerabilities.
Products
Firefox 2,316
Thunderbird 1,814
Firefox ESR 712
Firefox for iOS 63
Firefox for Android 33
Focus for Android 17
Thunderbird ESR 13
Focus for iOS 13
NSS 6
Focus 3
WebThings Gateway 2
Mozilla Bleach 2
Hubs Cloud 2
Mozilla VPN 2
Node-convict 1
Network Security Services (NSS) 1
thin-vec 1
Mozilla VPN 2.28.0 1
hawk 1
rhino 1
Firefox for 1
geckodriver 1
common-voice 1
Convict 1
Bugzilla 1
Persona 1
Network Security Services 1
Nunjucks 1
Klar for iOS 1
neqo 1
Mozilla VPN iOS 1.0.7 1
Mozilla VPN Windows 1
Mozilla VPN Android 1.1.0 1
sccache 1
Mozilla VPN 2.16.1 1
PollBot 1
Thunderbird < 102.8 0
Thunderbird < 102.9 0
Thunderbird < 102.9.1 0
Firefox < 110.1.0 Android 0
2,559 results · Feed
-
Critical 9.8
If an out-of-memory condition occurs at a specific point using allocations in the probabilistic heap checker, an assert…
-
Medium 4.3
In addition to detecting when a user was taking a screenshot (XXX), a website was able to overlay the 'My Shots' button…
-
Medium 5.3
A website was able to detect when a user took a screenshot of a page using the built-in Screenshot functionality in Fir…
-
Medium 5.3
If a specific sequence of actions is performed when opening a new tab, the triggering principal associated with the new…
-
High 7.0
Memory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of these bugs showed eviden…
-
High 8.6
By manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory leading to a potential…
-
Medium 4.7
By tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented a button that, if clic…
-
Medium 6.5
On Windows 10, when using the 'Save As' functionality, an attacker could have tricked the browser into saving the file …
-
Medium 6.1
Offscreen Canvas did not properly track cross-origin tainting, which could be used to access image data from another si…
-
High 7.5
Memory corruption in the networking stack could have led to a potentially exploitable crash. This vulnerability affects…
-
High 8.1
If a garbage collection was triggered at the right time, a use-after-free could have occurred during object transplant.…
-
Medium 4.3
By monitoring the time certain operations take, an attacker could have guessed which external protocol handlers were fu…
-
Medium 4.4
The file scheme of URLs would be hidden, resulting in potential spoofing of a website's address in the location bar Thi…
-
Critical 9.8
Memory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory corruption and we presume that …
-
High 8.2
A file dialog shown while in full-screen mode could have resulted in the window remaining disabled. This vulnerability …
-
High 7.5
When a network error occurred during page load, the prior content could have remained in view with a blank URL bar. Thi…
-
Medium 5.9
An iterator stop condition was missing when handling WASM code in the built-in profiler, potentially leading to invalid…
-
Medium 6.5
The `ShmemCharMapHashEntry()` code was susceptible to potentially undefined behavior by bypassing the move semantics fo…
-
Medium 5.9
An HTTP digest authentication nonce value was generated using `rand()` which could lead to predictable values. This vul…
-
High 8.6
A memory allocation check was missing which would lead to a use-after-free if the allocation failed. This could have tr…
-
Critical 9.8
Multiple WebRTC threads could have claimed a newly connected audio input leading to use-after-free. This vulnerability …
-
Medium 4.3
Different techniques existed to obscure the fullscreen notification in Firefox for Android. These could have led to pot…
-
High 8.1
Web application manifests were stored by using an insecure MD5 hash which allowed for a hash collision to overwrite ano…
-
Medium 5.9
When importing resources using Web Workers, error messages would distinguish the difference between `application/javasc…
-
Medium 6.1
A bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a user into granting pe…
-
High 8.8
When saving a page to PDF, certain font styles could have led to a potential use-after-free crash. This vulnerability a…
-
High 7.5
Memory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. Some of these bugs showed eviden…
-
Medium 5.6
PDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF
A type check was missing when handling fonts in PDF.js, which would allow arbitrary JavaScript execution in the PDF.js context. This vulnerability affects Firefox < 126, Firefox ESR < 115.11, and Thunderbird < 115.11.
-
Medium 4.3
If the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not properly deleted when the wi…
-
High 8.1
Memory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug showed evidence of memory …
-
High 8.1
Memory safety bugs present in Firefox 124. Some of these bugs showed evidence of memory corruption and we presume that …
-
Low 3.7
There was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server could abuse this to cr…
-
Medium 4.0
If an AlignedBuffer were assigned to itself, the subsequent self-move could result in an incorrect reference count and …
-
Critical 9.8
The executable file warning was not presented when downloading .xrm-ms files. *Note: This issue only affected Windows o…
-
Medium 5.3
The MarkStack assignment operator, part of the JavaScript engine, could access uninitialized memory if it were used in …
-
Medium 6.2
An out-of-memory condition during object initialization could result in an empty shape list. If the JIT subsequently tr…
-
Medium 5.9
On 32-bit versions there were integer-overflows that led to an out-of-bounds-read that potentially could be triggered b…
-
High 7.5
It was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This vulnerability affects …
-
High 8.8
A use-after-free could occur during WASM execution if garbage collection ran during the creation of an array. This vuln…
-
Medium 6.5
In certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds reads. This vulnerability…