Heap corruption via Spell check use-after-free
Published Jun 15, 2021 · Updated Aug 3, 2024
Use-after-free in Google Chrome Spell check before 91.0.4472.101 allows remote attackers to corrupt heap memory via a crafted HTML page. The Spell check component accesses an object after its heap allocation has been freed, but public Google material does not identify the object or function. Exploitation requires a user to install a malicious extension and open attacker-controlled HTML; the documented consequence is heap corruption, with no public determination of code execution versus a browser crash.
Summary
What happened
Use-after-free in Google Chrome Spell check before 91.0.4472.101 allows remote attackers to corrupt heap memory via a crafted HTML page. The Spell check component accesses an object after its heap allocation has been freed, but public Google material does not identify the object or function. Exploitation requires a user to install a malicious extension and open attacker-controlled HTML; the documented consequence is heap corruption, with no public determination of code execution versus a browser crash.
The record
- CVE
- CVE-2021-30549
- Published
- Jun 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 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 <91.0.4472.101
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