Heap corruption via freed Browser UI object
Published Aug 26, 2021 · Updated Aug 3, 2024
Use-after-free in Google Chrome's Browser UI before 92.0.4515.131 allows physically proximate attackers to trigger heap corruption. The Browser UI accesses an object after its memory has been freed; Google has not published the affected function or trigger. Physical access to the device is required, and the published record does not establish code execution or a more specific outcome.
Summary
What happened
Use-after-free in Google Chrome's Browser UI before 92.0.4515.131 allows physically proximate attackers to trigger heap corruption. The Browser UI accesses an object after its memory has been freed; Google has not published the affected function or trigger. Physical access to the device is required, and the published record does not establish code execution or a more specific outcome.
The record
- CVE
- CVE-2021-30597
- Published
- Aug 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 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.131
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.
Weakness, pattern, technique
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