Heap corruption via Splitscreen use-after-free
Published Jul 21, 2022 · Updated Aug 2, 2024
Use after free in Google Chrome Splitscreen before 99.0.4844.74 allows remote attackers to corrupt heap memory via crafted HTML on Chrome OS. Google identifies the Splitscreen component as reusing freed memory but has not published the freed object, triggering operation, or patch details. The path requires specific user interaction with the page and affects Chrome OS; the public record does not further bound the post-corruption impact.
Summary
What happened
Use after free in Google Chrome Splitscreen before 99.0.4844.74 allows remote attackers to corrupt heap memory via crafted HTML on Chrome OS. Google identifies the Splitscreen component as reusing freed memory but has not published the freed object, triggering operation, or patch details. The path requires specific user interaction with the page and affects Chrome OS; the public record does not further bound the post-corruption impact.
The record
- CVE
- CVE-2022-0974
- Published
- Jul 21, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2022CVE 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=unspecified <99.0.4844.74
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