Heap corruption via Safe Browsing use-after-free
Published Oct 8, 2021 · Updated Aug 4, 2024
Use-after-free in Google Chrome Safe Browsing before 94.0.4606.71 lets remote attackers with a compromised renderer corrupt the heap via crafted HTML. Google has not published the affected object, lifetime transition, or stale-pointer operation within the Safe Browsing component. A crafted page must first compromise Chrome's renderer; the published record does not establish code execution or sandbox escape.
Summary
What happened
Use-after-free in Google Chrome Safe Browsing before 94.0.4606.71 lets remote attackers with a compromised renderer corrupt the heap via crafted HTML. Google has not published the affected object, lifetime transition, or stale-pointer operation within the Safe Browsing component. A crafted page must first compromise Chrome's renderer; the published record does not establish code execution or sandbox escape.
The record
- CVE
- CVE-2021-37974
- Published
- Oct 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <94.0.4606.71
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