CVE-2020-16017: Use after free in site isolation
Google Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
Other sources
Use after free in site isolation in Google Chrome prior to 86.0.4240.198 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 90.0.4430.212-1~deb10u1Fixed in 116.0.5845.180-1~deb11u1Fixed in 120.0.6099.129-1~deb11u1Fixed in 119.0.6045.199-1~deb12u1Fixed in 120.0.6099.129-1~deb12u1Fixed in 120.0.6099.129-1 - Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 86.0.4240.198
Event History
Frequently Asked Questions
What is the severity of CVE-2020-16017?
CVE-2020-16017 is considered a high severity vulnerability due to its potential for remote exploitation and sandbox escape.
How do I fix CVE-2020-16017?
To mitigate CVE-2020-16017, users should upgrade to Google Chrome version 86.0.4240.198 or later.
What type of vulnerability is CVE-2020-16017?
CVE-2020-16017 is classified as a use-after-free vulnerability affecting the renderer process in Google Chrome.
Can CVE-2020-16017 be exploited remotely?
Yes, CVE-2020-16017 can be exploited remotely if an attacker tricks a user into visiting a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2020-16017?
CVE-2020-16017 affects Google Chrome versions prior to 86.0.4240.198.