Heap corruption via freed permission-prompt object
Published Jul 26, 2022 · Updated Aug 3, 2024
Use-after-free in Google Chrome Permission Prompts before 101.0.4951.64 allows remote attackers to corrupt heap memory through UI interactions. The Permission Prompts code accesses an object after its backing memory is freed, leaving a dangling reference that can corrupt reallocated heap data. Exploitation requires the user to perform specific interface actions; published details do not identify the exact prompt sequence or demonstrate a sandbox escape.
Summary
What happened
Use-after-free in Google Chrome Permission Prompts before 101.0.4951.64 allows remote attackers to corrupt heap memory through UI interactions. The Permission Prompts code accesses an object after its backing memory is freed, leaving a dangling reference that can corrupt reallocated heap data. Exploitation requires the user to perform specific interface actions; published details do not identify the exact prompt sequence or demonstrate a sandbox escape.
The record
- CVE
- CVE-2022-1635
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2022CVE 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 <101.0.4951.64
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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