ChromeOperating system · Google
CVE-2017-5085
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 Bookmarks in Google Chrome prior to 59 for iOS allowed a remote attacker who convinced the user to perform certain operations to run JavaScript on chrome:// pages via a crafted bookmark.
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 confidenceThis vulnerability in Google Chrome for iOS (versions prior to 59) allowed a remote attacker to execute arbitrary JavaScript on privileged chrome:// pages via a crafted bookmark. The flaw was an inappropriate implementation in the Bookmarks component that bypassed security restrictions on these internal pages, which normally should not execute user-supplied scripts.
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
ChromeOperating system
= 58.0.3029CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify installed Chrome for iOS versionOpen Google Chrome for iOS, tap the three-dot menu, go to Settings, then look for the version number under 'Chrome' or 'About Chrome'Affected if The version listed is 58.0.3029 or any version prior to 59.0.0.0
-
Confirm the specific affected versionVerify the exact version number shown in the About section matches 58.0.3029Affected if The version is exactly 58.0.3029, which is explicitly listed as affected
-
Determine if the Bookmarks feature is in useNavigate to the Bookmarks page in Chrome for iOS by tapping the star icon or accessing the bookmarks managerAffected if The user has created, imported, or syncs bookmarks to their device, as the exploit requires a crafted bookmark to be present
-
Check for unfamiliar or imported bookmarksReview the bookmark list for any unknown or suspicious bookmarks, particularly those that may have been imported from untrusted sourcesAffected if There are untrusted or unfamiliar bookmarks in the bookmark list that could contain malicious JavaScript
A user is affected if they are running Google Chrome for iOS version 58.0.3029 (or any version prior to 59) and have interacted with or imported a maliciously crafted bookmark.
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 dataUpdate Google Chrome for iOS to version 59 or later. Users should also be cautious about importing or clicking untrusted bookmarks, as the attack requires user interaction with a maliciously crafted bookmark.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5085 — 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-2017-5085 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