First published: Tue May 05 2020(Updated: )
Mozilla developers and community members Frederik Braun, Andrew McCreight, C.M.Chang, and Dan Minor reported memory safety bugs present in Firefox 75. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
Credit: security@mozilla.org
Affected Software | Affected Version | How to fix |
---|---|---|
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0+ | 76.0+ |
ubuntu/firefox | <76.0 | 76.0 |
ubuntu/firefox | <76.0+ | 76.0+ |
debian/firefox | 130.0-2 | |
Firefox | <76 | 76 |
Firefox | <76.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-12396 is classified as a high severity memory safety vulnerability in Firefox.
To fix CVE-2020-12396, update Firefox to version 76.0 or later.
CVE-2020-12396 affects Firefox versions prior to 76.0.
Yes, CVE-2020-12396 may allow attackers to exploit memory corruption leading to potential remote code execution.
There is no known workaround for CVE-2020-12396, so upgrading is the recommended action.