Sandbox escape via undisclosed Views implementation
Published Nov 12, 2024 · Updated Nov 12, 2024
Sandbox escape in Google Chrome before 131.0.6778.69 on Windows allows remote attackers to escape renderer isolation via crafted HTML. Google has not disclosed which Views code path performs the inappropriate operation or how the crafted page triggers it. Exploitation requires user interaction and prior compromise of the renderer process, after which the attacker can cross the browser sandbox boundary.
Summary
What happened
Sandbox escape in Google Chrome before 131.0.6778.69 on Windows allows remote attackers to escape renderer isolation via crafted HTML. Google has not disclosed which Views code path performs the inappropriate operation or how the crafted page triggers it. Exploitation requires user interaction and prior compromise of the renderer process, after which the attacker can cross the browser sandbox boundary.
The record
- CVE
- CVE-2024-11114
- Published
- Nov 12, 2024
- Updated
- Nov 12, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 12, 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 <131.0.6778.69
- Affected versionversion=131.0.6778.69 <131.0.6778.69
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.
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