ChromeWeb browser · Google
CVE-2020-6558
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 · uneditedInsufficient policy enforcement in iOSWeb in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.
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 confidenceInsufficient policy enforcement in iOSWeb in Google Chrome on iOS prior to version 85.0.4183.83 allows a remote attacker to bypass navigation restrictions by tricking users into visiting a crafted HTML page.
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
ChromeWeb browser
< 85.0.4183.83
Debian LinuxOperating system
= 10.0= 15.0= 15.1= 15.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Confirm Google Chrome on iOS is in useAsk users to verify they are using Google Chrome browser on an iOS device (iPhone/iPad). Check if Chrome iOS is deployed in your MDM or mobile device inventory.Affected if The target device runs Google Chrome on iOS as the browser application.
-
Check Chrome iOS version numberOn the iOS device, open Chrome, tap the three dots menu > Settings > Chrome version. Alternatively, check via MDM or device management console.Affected if The displayed version number is lower than 85.0.4183.83 (e.g., 84.x.x.x or earlier).
-
Verify navigation policy configurationThis vulnerability concerns iOSWeb navigation policy enforcement. Review Chrome iOS security settings or enterprise policies if deployed. The flaw allows crafted HTML to bypass navigation restrictions.Affected if Navigation restrictions are configured in Chrome iOS (via MDM or enterprise policy) and the browser version is below 85.0.4183.83, making the bypass applicable.
A user is affected if they run Google Chrome on iOS with a version lower than 85.0.4183.83 and navigation restrictions are in place that could be bypassed by a crafted HTML page.
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.
From vendor data85.0.4183.83
Update Google Chrome on iOS to version 85.0.4183.83 or later to obtain the patched browser. Organizations should deploy this update via MDM or ensure users update through the App Store.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6558 — 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-2020-6558 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