Sandbox escape via Autofill use-after-free
Published Jan 8, 2021 · Updated Aug 3, 2024
Use-after-free in Google Chrome's Autofill component before 87.0.4280.141 allows remote attackers to escape the sandbox via crafted HTML. Google's public advisory identifies Autofill and use-after-free but does not disclose the freed object, faulty lifetime operation, or triggering sequence. Exploitation requires an already compromised renderer and user interaction with crafted HTML, and successful exploitation crosses the renderer sandbox boundary.
Summary
What happened
Use-after-free in Google Chrome's Autofill component before 87.0.4280.141 allows remote attackers to escape the sandbox via crafted HTML. Google's public advisory identifies Autofill and use-after-free but does not disclose the freed object, faulty lifetime operation, or triggering sequence. Exploitation requires an already compromised renderer and user interaction with crafted HTML, and successful exploitation crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2021-21106
- Published
- Jan 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1068
- Attack vector
- network
- Privileges
- Unavailable
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?
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