Heap corruption via crafted script in V8
Published Feb 22, 2021 · Updated Aug 3, 2024
Heap buffer overflow in V8 in Google Chrome before 88.0.4324.182 allows remote attackers to corrupt heap memory via a crafted script. Google identifies V8 and issue 1177341 but does not disclose the affected function or incorrect bounds operation. Exploitation requires a victim to process attacker-controlled script content, with memory corruption occurring inside the browser process.
Summary
What happened
Heap buffer overflow in V8 in Google Chrome before 88.0.4324.182 allows remote attackers to corrupt heap memory via a crafted script. Google identifies V8 and issue 1177341 but does not disclose the affected function or incorrect bounds operation. Exploitation requires a victim to process attacker-controlled script content, with memory corruption occurring inside the browser process.
The record
- CVE
- CVE-2021-21156
- Published
- Feb 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <88.0.4324.182
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Chrome Array Transfer Bypassproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo