dbcve.org
ChromeWeb browser · Google

CVE-2016-5173

HIGH · 7.1 CVSS v3.0 Published 2016-09-25
Fix available
A fix is available. Upgrade to after 53.0.2785.101 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
The extensions subsystem in Google Chrome before 53.0.2785.113 does not properly restrict access to Object.prototype, which allows remote attackers to load unintended resources, and consequently trigger unintended JavaScript function calls and bypass the Same Origin Policy via an indirect interception attack.

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 confidence

Google Chrome's extensions subsystem before 53.0.2785.113 improperly restricted access to Object.prototype, allowing remote attackers to load unintended resources, trigger unauthorized JavaScript function calls, and bypass the Same Origin Policy via indirect interception attacks.

MitigationUpdate Chrome to version 53.0.2785.113 or later. Review and test any custom extensions for compatibility with the patched version.

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
Affected:<= 53.0.2785.101

CVSS 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
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Open Chrome and navigate to version information
    In the Chrome address bar, navigate to chrome://settings/help OR click the three-dot menu > Help > About Google Chrome. The version number will be displayed on that page.
    Affected if The displayed version number is 53.0.2785.101 or lower (for example, 53.0.2785.92, 52.0.2743.116, etc.)
  2. Alternative method - check via chrome://version
    In the Chrome address bar, navigate to chrome://version. This page displays detailed version information including the Chrome version, OS, and JavaScript version.
    Affected if The version shown (the first line, like 'Chrome/53.0.2785.101') is 53.0.2785.101 or lower.
  3. Confirm you are checking the correct Chrome installation
    If you have multiple Chrome installations (e.g., stable, beta, dev channels), check each one individually by opening that specific Chrome version and following step 1 or 2.
    Affected if Any installed Chrome channel (stable, beta, dev, Canary) shows version 53.0.2785.101 or lower.

You are affected if any installed instance of Google Chrome displays version 53.0.2785.101 or lower on the chrome://settings/help or chrome://version page.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 53.0.2785.101
Interim mitigation

Update Chrome to version 53.0.2785.113 or later. Review and test any custom extensions for compatibility with the patched version.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5173 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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