Vulnerabilidades em mozilla
2.453 resultadosAnálise Vexday
A Mozilla apresenta um perfil de risco baixo com apenas 3 vulnerabilidades catalogadas, nenhuma sob exploração ativa ou crítica. A fraqueza dominante identificada é CWE-400 (Uncontrolled Resource Consumption), que tipicamente afeta disponibilidade; a ausência de publicações recentes sugere que o risco atual não é imediato.
CVE-2020-15681—When multiple WASM threads had a reference to a module, and were looking up exported functions, one WASM thread could have overwritten anothEPSS 1.1%CVE-2017-5417—When dragging content from the primary browser pane to the addressbar on a malicious site, it is possible to change the addressbar so that tEPSS 1.1%CVE-2018-5138—A spoofing vulnerability can occur when a malicious site with an extremely long domain name is opened in an Android Custom Tab (a browser paEPSS 1.1%CVE-2022-34470CRITICALSession history navigations may have led to a use-after-free and potentially exploitable crash. This vulnerability affects Firefox < 102, FiEPSS 1.1%CVE-2019-11720—Some unicode characters are incorrectly treated as whitespace during the parsing of web content instead of triggering parsing errors. This aEPSS 1.1%CVE-2021-38505—Microsoft introduced a new feature in Windows 10 known as Cloud Clipboard which, if enabled, will record data copied to the clipboard to theEPSS 1.1%CVE-2019-9806—A vulnerability exists during authorization prompting for FTP transaction where successive modal prompts are displayed and cannot be immediaEPSS 1.1%CVE-2022-40960MEDIUMConcurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a use-after-free causing a potentially exploitaEPSS 1.1%CVE-2021-23988—Mozilla developers reported memory safety bugs present in Firefox 86. Some of these bugs showed evidence of memory corruption and we presumeEPSS 1.1%CVE-2017-5453—A mechanism to inject static HTML into the RSS reader preview page due to a failure to escape characters sent as URL parameters for a feed'sEPSS 1.1%CVE-2022-45406CRITICALIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be deleted while references to it lived on EPSS 1.1%CVE-2020-15670—Mozilla developers reported memory safety bugs present in Firefox for Android 79. Some of these bugs showed evidence of memory corruption anEPSS 1.1%CVE-2024-5688HIGHIf a garbage collection was triggered at the right time, a use-after-free could have occurred during object transplant. This vulnerability aEPSS 1.1%CVE-2021-4129CRITICALMozilla developers and community members Julian Hector, Randell Jesup, Gabriele Svelto, Tyson Smith, Christian Holler, and Masayuki Nakano rEPSS 1.1%CVE-2019-11751—Logging-related command line parameters are not properly sanitized when Firefox is launched by another program, such as when a user clicks oEPSS 1.1%CVE-2017-7782—An error in the "WindowsDllDetourPatcher" where a RWX ("Read/Write/Execute") 4k block is allocated but never protected, violating DEP protecEPSS 1.1%CVE-2021-23953—If a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking cross-origin information, when said informaEPSS 1.1%CVE-2022-29917CRITICALMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team reported memory safety bugs present in FirefoxEPSS 1.1%CVE-2020-26951—A parsing and event loading mismatch in Firefox's SVG code could have allowed load events to fire, even after sanitization. An attacker alreEPSS 1.1%CVE-2020-35114—Mozilla developers reported memory safety bugs present in Firefox 83. Some of these bugs showed evidence of memory corruption and we presumeEPSS 1.0%