Mozilla CVEs
2,561 CVEs and advisories name Mozilla as an affected vendor, 9 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2021-43541When invoking protocol handlers for external protocols, a supplied parameter URL containing spaces was not properly escaped.
- CVE-2021-43542Using XMLHttpRequest, an attacker could have identified installed applications by probing error messages for loading external protocols.
- CVE-2021-43543Documents loaded with the CSP sandbox directive could have escaped the sandbox's script restriction by embedding additional content.
- CVE-2021-43544When receiving a URL through a SEND intent, Firefox would have searched for the text, but subsequent usages of the address bar might have ca
- CVE-2021-43545Using the Location API in a loop could have caused severe application hangs and crashes.
- CVE-2021-43546It was possible to recreate previous cursor spoofing attacks against users with a zoomed native cursor.
- CVE-2021-43527NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-
- CVE-2021-29991Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers.
- CVE-2021-29993Firefox for Android allowed navigations through the `intent://` protocol, which could be used to cause crashes and UI spoofs.
- CVE-2021-38491Mixed-content checks were unable to analyze opaque origins which led to some mixed content being loaded.
- CVE-2021-38492When delegating navigations to the operating system, Firefox would accept the `mk` scheme which might allow attackers to launch pages and ex
- CVE-2021-38493Mozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13.
- CVE-2021-38494Mozilla developers reported memory safety bugs present in Firefox 91.
- CVE-2021-38495Mozilla developers reported memory safety bugs present in Thunderbird 78.13.0.
- CVE-2021-38496During operations on MessageTasks, a task may have been removed while it was still scheduled, resulting in memory corruption and a potential
- CVE-2021-38497Through use of reportValidity() and window.open(), a plain-text validation message could have been overlaid on another origin, leading to po
- CVE-2021-38498During process shutdown, a document could have caused a use-after-free of a languages service object, leading to memory corruption and a pot
- CVE-2021-38499Mozilla developers reported memory safety bugs present in Firefox 92.
- CVE-2021-38500Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1.
- CVE-2021-38501Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1.
- CVE-2021-38502Thunderbird ignored the configuration to require STARTTLS security for an SMTP connection.
- CVE-2021-29980Uninitialized memory in a canvas object could have caused an incorrect free() leading to memory corruption and a potentially exploitable cra
- CVE-2021-29981An issue present in lowering/register allocation could have led to obscure but deterministic register confusion failures in JITted code that
- CVE-2021-29982Due to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object, resulting in the potential leak of a singl
- CVE-2021-29983Firefox for Android could get stuck in fullscreen mode and not exit it even after normal interactions that should cause it to exit.
- CVE-2021-29984Instruction reordering resulted in a sequence of instructions that would cause an object to be incorrectly considered during garbage collect
- CVE-2021-29985A use-after-free vulnerability in media channels could have led to memory corruption and a potentially exploitable crash.
- CVE-2021-29986A suspected race condition when calling getaddrinfo led to memory corruption and a potentially exploitable crash.
- CVE-2021-29987After requesting multiple permissions, and closing the first permission panel, subsequent permission panels will be displayed in a different
- CVE-2021-29988Firefox incorrectly treated an inline list-item element as a block element, resulting in an out of bounds read or memory corruption, and a p