User-assisted sandbox escape
Published Jul 16, 2024 · Updated Aug 2, 2024
Insufficient data validation in Google Chrome before 117.0.5938.62 allows attackers to escape the sandbox via a malicious file. The flaw resides in Permission Prompts, but Google has not published which file field is accepted incorrectly or how that value crosses the sandbox boundary. Exploitation requires convincing a user to install a malicious app and process its malicious file; the documented consequence is escape from Chrome's sandbox.
Summary
What happened
Insufficient data validation in Google Chrome before 117.0.5938.62 allows attackers to escape the sandbox via a malicious file. The flaw resides in Permission Prompts, but Google has not published which file field is accepted incorrectly or how that value crosses the sandbox boundary. Exploitation requires convincing a user to install a malicious app and process its malicious file; the documented consequence is escape from Chrome's sandbox.
The record
- CVE
- CVE-2023-7012
- Published
- Jul 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-138, CWE-20, T1204.002
- 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 <117.0.5938.62
- Affected versionversion=117.0.5938.62 <117.0.5938.62
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