Site-isolation bypass via flawed service-worker handling
Published Dec 23, 2021 · Updated Aug 4, 2024
Inappropriate service-worker handling in Google Chrome before 96.0.4664.45 allows remote attackers to bypass site isolation. Google identifies the service-worker implementation but has not published the incorrect operation that lets crafted HTML cross the boundary. Exploitation requires prior renderer compromise and defeats origin separation without a reported browser sandbox escape or host-code execution.
Summary
What happened
Inappropriate service-worker handling in Google Chrome before 96.0.4664.45 allows remote attackers to bypass site isolation. Google identifies the service-worker implementation but has not published the incorrect operation that lets crafted HTML cross the boundary. Exploitation requires prior renderer compromise and defeats origin separation without a reported browser sandbox escape or host-code execution.
The record
- CVE
- CVE-2021-38010
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <96.0.4664.45
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