ChromeWeb browser · Google
CVE-2016-5143
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 · uneditedThe Developer Tools (aka DevTools) subsystem in Blink, as used in Google Chrome before 52.0.2743.116, mishandles the script-path hostname, remoteBase parameter, and remoteFrontendUrl parameter, which allows remote attackers to bypass intended access restrictions via a crafted URL, a different vulnerability than CVE-2016-5144.
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 confidenceA vulnerability in Chrome's Developer Tools (Blink) allows remote attackers to bypass access restrictions by crafting malicious URLs with specific parameters (remoteBase, remoteFrontendUrl, script-path hostname). This enables unauthorized access to DevTools functionality.
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
<= 52.0.2743.82CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check installed Chrome versionOpen Chrome, click the menu (three dots) > Help > About Google Chrome. The version number is displayed on this page.Affected if The version listed is 52.0.2743.82 or lower
-
Confirm version number preciselyCompare your exact version against the affected range. Note that versions like 52.0.2743.82, 52.0.2743.75, or any 52.x version below 52.0.2743.116 are within the affected range.Affected if Your version number is less than or equal to 52.0.2743.82
-
Check for remote debugging configurationInspect Chrome launch arguments or policies. Remote debugging is typically enabled via --remote-debugging-port=PORT flag or through enterprise policies allowing remote DevTools connections.Affected if Remote debugging is enabled or configured, making the DevTools endpoint accessible to remote attackers
You are affected if your Chrome version is 52.0.2743.82 or lower and remote debugging or remote DevTools access is enabled in your environment.
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 · scopedUpdate Google Chrome to version 52.0.2743.116 or later to patch this vulnerability. Users should ensure automatic updates are enabled or manually check for updates.
Chrome 52.0.2743.116 or later (recommended: latest stable release)
- Open Chrome and navigate to chrome://settings/help to check your current version
- If the version is 52.0.2743.82 or earlier, click 'Update Google Chrome' to receive the security patch
- Alternatively, download and install the latest Chrome version from https://www.google.com/chrome/
- Restart Chrome after the update completes
- Verify the update by revisiting chrome://settings/help to confirm version 52.0.2743.116 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5143 — 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-2016-5143 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