CVE-2021-37978: Heap buffer overflow in Blink
Heap buffer overflow in Blink in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 94.0.4606.81 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20211006-r1 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20211006-r3 - 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.
Frequently Asked Questions
What is the severity of CVE-2021-37978?
CVE-2021-37978 has a high severity rating due to its potential for remote exploitation through unauthorized access.
How do I fix CVE-2021-37978?
To fix CVE-2021-37978, users should update Google Chrome or Chromium to version 94.0.4606.81 or later.
Which versions of Google Chrome are affected by CVE-2021-37978?
CVE-2021-37978 affects all versions of Google Chrome prior to 94.0.4606.81.
How can CVE-2021-37978 be exploited?
An attacker could exploit CVE-2021-37978 by sending a specially crafted HTML page that triggers a heap buffer overflow.
What is the primary component vulnerable in CVE-2021-37978?
The primary component vulnerable in CVE-2021-37978 is the Blink rendering engine in Google Chrome.