Local access-control bypass via weakened DCOM permissions
Published Sep 8, 2021 · Updated Aug 3, 2024
Access control bypass in Google Chrome before 1.0.2.0 allows local users to access protected DCOM objects through weakened permissions. The Windows ChromeOS Readiness Tool installer loosens discretionary access controls on two DCOM objects instead of preserving their restricted access rights. Exploitation requires local low-privileged access, and published details do not identify the objects or the operations they expose.
Summary
What happened
Access control bypass in Google Chrome before 1.0.2.0 allows local users to access protected DCOM objects through weakened permissions. The Windows ChromeOS Readiness Tool installer loosens discretionary access controls on two DCOM objects instead of preserving their restricted access rights. Exploitation requires local low-privileged access, and published details do not identify the objects or the operations they expose.
The record
- CVE
- CVE-2021-30605
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-287
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 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 <1.0.2.0
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