Heap corruption via Exosphere use-after-free
Published Jan 2, 2023 · Updated Oct 22, 2024
Use-after-free in Google Chrome's Exosphere on ChromeOS and Lacros before 104.0.5112.79 allows remote attackers to corrupt heap memory. The public record identifies Exosphere but does not disclose the freed object or the operation that later reuses it. Exploitation requires crafted UI interactions by the user, after which the stale-pointer access can corrupt the browser heap.
Summary
What happened
Use-after-free in Google Chrome's Exosphere on ChromeOS and Lacros before 104.0.5112.79 allows remote attackers to corrupt heap memory. The public record identifies Exosphere but does not disclose the freed object or the operation that later reuses it. Exploitation requires crafted UI interactions by the user, after which the stale-pointer access can corrupt the browser heap.
The record
- CVE
- CVE-2022-2742
- Published
- Jan 2, 2023
- Updated
- Oct 22, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, CWE-362, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2023CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=0 <104.0.5112.79
- Affected versionversion=unspecified <104.0.5112.79
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