CVE-2021-4320: Use after free in Blink
Use after free in Blink in Google Chrome prior to 92.0.4515.107 allowed a remote attacker who had compromised the renderer process to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 92.0.4515.107 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2021-30565
- CVE-2021-30566
- CVE-2021-30567
- CVE-2021-30568
- CVE-2021-30569
- CVE-2021-30571
- CVE-2021-30572
- CVE-2021-30573
- CVE-2021-30574
- CVE-2021-30575
- CVE-2021-30576
- CVE-2021-30577
- CVE-2021-30578
- CVE-2021-30579
- CVE-2021-30580
- CVE-2021-30581
- CVE-2021-30582
- CVE-2021-30583
- CVE-2021-30584
- CVE-2021-30585
- CVE-2021-30586
- CVE-2021-30587
- CVE-2021-30588
- CVE-2021-30589
Frequently Asked Questions
What is the severity of CVE-2021-4320?
CVE-2021-4320 has a high severity rating due to its potential for arbitrary read/write access.
How do I fix CVE-2021-4320?
To fix CVE-2021-4320, upgrade Google Chrome to version 92.0.4515.107 or later.
What type of vulnerability is CVE-2021-4320?
CVE-2021-4320 is classified as a use after free vulnerability in the Blink rendering engine.
Who is affected by CVE-2021-4320?
Users running Google Chrome versions prior to 92.0.4515.107 are vulnerable to CVE-2021-4320.
What can attackers do with CVE-2021-4320?
Attackers can exploit CVE-2021-4320 to perform arbitrary read/write operations through a specially crafted HTML page.