CVE-2020-16024

Description

Heap buffer overflow in UI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.

Category

9.6
CVSS
Severity: Critical
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.88% Top 30%
Vendor Advisory googleblog.com Vendor Advisory crbug.com
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_17.html release notes vendor advisory
https://crbug.com/1147430 permissions required vendor advisory
http://packetstormsecurity.com/files/161353/Chrome-SkBitmapOperations-UnPreMultiply-Heap-Buffer-Overflow.html vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2020-16024?
CVE-2020-16024 has been scored as a critical severity vulnerability.
How to fix CVE-2020-16024?
To fix CVE-2020-16024, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-16024 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-16024 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-16024?
CVE-2020-16024 affects Google Chrome.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.