Heap buffer overflow in V8 in Google Chrome prior to 88.0.4324.150 allowed a remote attacker to potentially exploit heap corruption via a cr
Affects Google Chrome versions before 88.0.4324.150, with the V8 JavaScript engine as the affected component. Fixed in Chrome 88.0.4324.150.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 88.0.4324.150
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Google Chrome's V8 JavaScript engine contains a heap buffer overflow that a remote attacker could exploit by tricking a user into opening a specially crafted web page. Successful exploitation could corrupt memory and potentially allow the attacker to run malicious code or compromise the browser.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Heap buffer overflow in V8 in Google Chrome prior to 88.0.4324.150 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Google Chrome
From unspecified · fixed in 88.0.4324.150
References 7
crbug.com
chromereleases.googleblog.com
lists.fedoraproject.org
debian.org
security.gentoo.org
packetstormsecurity.com
Questions about CVE-2021-21148
What should I do about it?
Update Google Chrome to 88.0.4324.150 or later. The fix is only available in that version or newer, and no workaround is listed.Source: lists.fedoraproject.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data