Heap corruption via protocol-handler use-after-free
Published Aug 3, 2021 · Updated Aug 3, 2024
Use-after-free in Google Chrome protocol handling before 92.0.4515.107 allows remote attackers to trigger heap corruption via crafted HTML. The protocol-handling component accesses an object after its lifetime has ended; public records do not identify the affected function or object. User interaction is required, and public sources do not document the resulting control over browser execution or any sandbox escape.
Summary
What happened
Use-after-free in Google Chrome protocol handling before 92.0.4515.107 allows remote attackers to trigger heap corruption via crafted HTML. The protocol-handling component accesses an object after its lifetime has ended; public records do not identify the affected function or object. User interaction is required, and public sources do not document the resulting control over browser execution or any sandbox escape.
The record
- CVE
- CVE-2021-30574
- Published
- Aug 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 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 <92.0.4515.107
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