Sandbox escape via undisclosed Skia implementation flaw
Published Jul 16, 2024 · Updated Aug 2, 2024
Sandbox escape in Skia in Google Chrome before 115.0.5790.98 allows remote attackers to escape a compromised renderer via crafted HTML. Google identifies the locus only as an inappropriate Skia implementation; the restricted issue does not publicly disclose the faulty operation on untrusted input. Exploitation requires both user interaction with attacker-controlled HTML and an already-compromised renderer, after which code can cross the browser sandbox boundary.
Summary
What happened
Sandbox escape in Skia in Google Chrome before 115.0.5790.98 allows remote attackers to escape a compromised renderer via crafted HTML. Google identifies the locus only as an inappropriate Skia implementation; the restricted issue does not publicly disclose the faulty operation on untrusted input. Exploitation requires both user interaction with attacker-controlled HTML and an already-compromised renderer, after which code can cross the browser sandbox boundary.
The record
- CVE
- CVE-2023-4860
- Published
- Jul 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-303, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE 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=0 <115.0.5790.98
- Affected versionversion=115.0.5790.98 <115.0.5790.98
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