Heap corruption via ANGLE out-of-bounds access
Published Oct 8, 2021 · Updated Aug 3, 2024
Out-of-bounds memory access in ANGLE in Google Chrome before 93.0.4577.82 allows remote attackers to trigger heap corruption via crafted HTML. The public record does not identify the ANGLE code locus or the specific operation that accesses memory outside its intended bounds. Exploitation requires a user to load attacker-controlled HTML; Google has not published a more specific consequence of the resulting browser-process heap corruption.
Summary
What happened
Out-of-bounds memory access in ANGLE in Google Chrome before 93.0.4577.82 allows remote attackers to trigger heap corruption via crafted HTML. The public record does not identify the ANGLE code locus or the specific operation that accesses memory outside its intended bounds. Exploitation requires a user to load attacker-controlled HTML; Google has not published a more specific consequence of the resulting browser-process heap corruption.
The record
- CVE
- CVE-2021-30626
- Published
- Oct 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 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 <93.0.4577.82
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
No public exploit references are available in this record.
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