Heap corruption via Splitscreen use-after-free
Published Aug 1, 2023 · Updated Aug 2, 2024
Use-after-free in Ash Splitscreen in Google Chrome before 115.0.5790.131 on ChromeOS allows remote attackers to corrupt heap memory. Google identifies a freed-object lifetime error in Ash but keeps the underlying bug details restricted, leaving the precise invalid operation undisclosed. Exploitation requires a user to perform specific crafted UI interactions; public sources establish heap corruption but do not establish code execution.
Summary
What happened
Use-after-free in Ash Splitscreen in Google Chrome before 115.0.5790.131 on ChromeOS allows remote attackers to corrupt heap memory. Google identifies a freed-object lifetime error in Ash but keeps the underlying bug details restricted, leaving the precise invalid operation undisclosed. Exploitation requires a user to perform specific crafted UI interactions; public sources establish heap corruption but do not establish code execution.
The record
- CVE
- CVE-2023-3729
- Published
- Aug 1, 2023
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=115.0.5790.131 <115.0.5790.131
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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