CVE-2020-12407

MediumCVSS 6.5/10Last modified Jun 17, 2026

Description

Mozilla Developer Nicolas Silva found that when using WebRender, Firefox would under certain conditions leak arbitrary GPU memory to the visible screen. The leaked memory content was visible to the user, but not observable from web content. This vulnerability affects Firefox < 77.

Metrics

CVSS 3.1 6.5/10CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Weakness enumeration

Affected software

No affected versions have been published.

Timeline

Published
Jul 9, 2020
Last modified
Jun 17, 2026
NVD status
Modified

Related CVEs from 2020

CVE-2020-124086.5When browsing a document hosted on an IP address, an attacker could insert certain characters to flip domain and path information in the addCVE-2020-124098.8When using certain blank characters in a URL, they where incorrectly rendered as spaces instead of an encoded URL. This vulnerability affectCVE-2020-12417.8A security feature bypass vulnerability exists when Windows Kernel fails to properly sanitize certain parameters.To exploit the vulnerabilitCVE-2020-124108.8Mozilla developers reported memory safety bugs present in Firefox 76 and Firefox ESR 68.8. Some of these bugs showed evidence of memory corrCVE-2020-124118.8Mozilla developers reported memory safety bugs present in Firefox 76. Some of these bugs showed evidence of memory corruption and we presumeCVE-2020-124124.3By navigating a tab using the history API, an attacker could cause the address bar to display the incorrect domain (with the https:// schemeCVE-2020-124135.9The Raccoon attack is a timing attack on DHE ciphersuites inherit in the TLS specification. To mitigate this vulnerability, Firefox disabledCVE-2020-124146.5IndexedDB should be cleared when leaving private browsing mode and it is not, the API for WKWebViewConfiguration was being used incorrectly CVE-2020-124156.5When "%2F" was present in a manifest URL, Firefox's AppCache behavior may have become confused and allowed a manifest to be served from a suCVE-2020-124168.8A VideoStreamEncoder may have been freed in a race condition with VideoBroadcaster::AddOrUpdateSink, resulting in a use-after-free, memory cCVE-2020-124178.8Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in memory corruption and a poCVE-2020-124186.5Manipulating individual parts of a URL object could have caused an out-of-bounds read, leaking process memory to malicious JavaScript. This
CVE-2020-12407: Medium severity, CVSS 6.5 | Vulnix