Heap corruption via stale animation execution context
Published Mar 9, 2021 · Updated Aug 3, 2024
Use-after-free in Blink in Google Chrome before 89.0.4389.72 allows remote attackers to trigger heap corruption via crafted HTML. Animatable::animate checks its execution context only on entry, although parsing attacker-controlled keyframes can invalidate that context before later code uses it. Exploitation requires a user to load the crafted page; the documented trigger crashes the renderer, and the CVE record identifies heap corruption as the broader consequence.
Summary
What happened
Use-after-free in Blink in Google Chrome before 89.0.4389.72 allows remote attackers to trigger heap corruption via crafted HTML. Animatable::animate checks its execution context only on entry, although parsing attacker-controlled keyframes can invalidate that context before later code uses it. Exploitation requires a user to load the crafted page; the documented trigger crashes the renderer, and the CVE record identifies heap corruption as the broader consequence.
The record
- CVE
- CVE-2021-21188
- Published
- Mar 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 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 <89.0.4389.72
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