Heap corruption via DevTools use-after-free
Published Apr 30, 2021 · Updated Aug 3, 2024
Use-after-free in DevTools in Google Chrome before 90.0.4430.93 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies two restricted Chromium issue records but has not published the freed object's lifetime error or responsible function. A target must load attacker-controlled content; the documented consequence is heap corruption, not confirmed code execution outside the browser.
Summary
What happened
Use-after-free in DevTools in Google Chrome before 90.0.4430.93 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies two restricted Chromium issue records but has not published the freed object's lifetime error or responsible function. A target must load attacker-controlled content; the documented consequence is heap corruption, not confirmed code execution outside the browser.
The record
- CVE
- CVE-2021-21232
- Published
- Apr 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 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 <90.0.4430.93
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