Browser code execution via freed screen-capture object
Published Apr 9, 2021 · Updated Aug 3, 2024
Use after free in Google Chrome screen capture before 89.0.4389.114 allows remote attackers to corrupt heap memory via a crafted HTML page. The screen-capture flow retains and later accesses an object after its lifetime ends when the requesting page closes before approval. Exploitation requires a user to open the page and approve screen sharing after the page closes; successful heap corruption can execute code in the browser context.
Summary
What happened
Use after free in Google Chrome screen capture before 89.0.4389.114 allows remote attackers to corrupt heap memory via a crafted HTML page. The screen-capture flow retains and later accesses an object after its lifetime ends when the requesting page closes before approval. Exploitation requires a user to open the page and approve screen sharing after the page closes; successful heap corruption can execute code in the browser context.
The record
- CVE
- CVE-2021-21194
- Published
- Apr 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 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 <89.0.4389.114
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.
Public exploit references
- Chromium issue 1181228 reproduction caseproof of concept · demonstrated
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