CVE-2021-21155: Heap buffer overflow in Tab Strip
Published Feb 7, 2021
·Updated
Heap buffer overflow in Tab Strip in Google Chrome on Windows prior to 88.0.4324.182 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Credit
Khalil Zhani
Affected Software
6 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1118.0.5993.70-1~deb11u1116.0.5845.180-1~deb12u1118.0.5993.70-1~deb12u1118.0.5993.70-1
Google Chrome<88.0.4324.182
88.0.4324.182
Google Chrome<88.0.4324.182
Microsoft Windows
fedoraproject fedora=32
fedoraproject fedora=33
Remediation
Patch Available
Event History
Feb 7, 2021
CVE Published
12:00 AM
Feb 22, 2021
CVE Published
via MITRE·09:20 PM
Data Sourced
via MITRE·09:20 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2021-21155?
CVE-2021-21155 has a high severity rating due to its potential for remote code execution through a heap buffer overflow.
2
How do I fix CVE-2021-21155?
To mitigate CVE-2021-21155, update Google Chrome to version 88.0.4324.182 or later.
3
Which versions of Google Chrome are affected by CVE-2021-21155?
Versions of Google Chrome prior to 88.0.4324.182 are affected by CVE-2021-21155.
4
Can CVE-2021-21155 be exploited remotely?
Yes, CVE-2021-21155 can be exploited remotely by an attacker who compromises a renderer process.
5
Is there a workaround for CVE-2021-21155?
The best approach to avoid CVE-2021-21155 is to ensure that Google Chrome is updated to the latest version.