Sandbox escape via WebUI policy enforcement failure
Published Jan 8, 2021 · Updated Aug 3, 2024
Insufficient policy enforcement in Google Chrome WebUI before 87.0.4280.141 allows attackers to escape the browser sandbox via a crafted extension. Google identifies WebUI as the locus, but the restricted bug record leaves the failed policy check and crafted-extension trigger undisclosed. Exploitation requires persuading a user to install the malicious extension; public sources do not identify the resources reachable after escape.
Summary
What happened
Insufficient policy enforcement in Google Chrome WebUI before 87.0.4280.141 allows attackers to escape the browser sandbox via a crafted extension. Google identifies WebUI as the locus, but the restricted bug record leaves the failed policy check and crafted-extension trigger undisclosed. Exploitation requires persuading a user to install the malicious extension; public sources do not identify the resources reachable after escape.
The record
- CVE
- CVE-2021-21111
- Published
- Jan 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-1021, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <87.0.4280.141
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