Chrome Os Readiness ToolWeb browser · Google
CVE-2021-30605
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInappropriate implementation in the ChromeOS Readiness Tool installer on Windows prior to 1.0.2.0 loosens DCOM access rights on two objects allowing an attacker to potentially bypass discretionary access controls.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ChromeOS Readiness Tool installer for Windows versions prior to 1.0.2.0 contains an inappropriate implementation that loosens DCOM (Distributed Component Object Model) access rights on two specific objects, weakening their security permissions and potentially allowing an attacker to bypass discretionary access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Chrome Os Readiness ToolWeb browser
< 1.0.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ChromeOS Readiness Tool installationCheck for the presence of Google ChromeOS Readiness Tool on the Windows system by searching in Program Files, Program Files (x86), or using Add/Remove Programs. The tool is typically installed as 'ChromeOS Readiness Tool' or similar.Affected if The tool is installed on the system
-
Check installed versionLocate the installed executable or check the version through Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Compare the version number to 1.0.2.0.Affected if The installed version is less than 1.0.2.0
-
Inspect DCOM access control settingsOpen Component Services (dcomcnfg.exe), navigate to Component Services > Computers > My Computer > DCOM Config. Identify any objects modified by the ChromeOS Readiness Tool installer and examine their Security settings under the 'Security' tab, specifically the Access Permissions and Launch and Activation Permissions.Affected if DCOM objects show loosened or overly permissive access rights compared to default Windows hardened settings, particularly on objects related to the ChromeOS Readiness Tool installation
A user is affected if the ChromeOS Readiness Tool is installed with a version prior to 1.0.2.0 and the installer modified DCOM access control permissions on system objects.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.0.2.0
Upgrade the ChromeOS Readiness Tool installer to version 1.0.2.0 or later to obtain the corrected DCOM access control settings.
1.0.2.0
- Check the current installed version of ChromeOS Readiness Tool on Windows systems
- Download ChromeOS Readiness Tool version 1.0.2.0 or later from the official Google source (Chrome Enterprise or Chrome OS help pages)
- Uninstall the current vulnerable version of ChromeOS Readiness Tool
- Install the fixed version 1.0.2.0
- Verify the installed version is 1.0.2.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome Os Readiness Tool
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-30605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data