Linux DesktopOperating system · Redhat
CVE-2018-6101
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 · uneditedA lack of host validation in DevTools in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to execute arbitrary code via a crafted HTML page, if the user is running a remote DevTools debugging server.
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 confidenceGoogle Chrome DevTools prior to version 66.0.3359.117 lacked proper host validation, allowing a remote attacker to execute arbitrary code via a crafted HTML page when the user runs a remote DevTools debugging server.
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
Linux DesktopOperating system
= 6.0
Linux ServerOperating system
= 6.0
Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 8.0= 9.0
ChromeWeb browser
< 66.0.3359.117CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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, go to Menu > Help > About Google Chrome, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Version is earlier than 66.0.3359.117
-
Identify if remote DevTools debugging is enabledCheck Chrome launch arguments for '--remote-debugging-port' flag or inspect any custom startup scripts/configurations that start Chrome with remote debuggingAffected if Chrome is launched with '--remote-debugging-port' or '--remote-debugging-host' flags exposing debugging to non-localhost
-
Verify network exposure of DevToolsIf remote debugging is enabled, check if the debugging port is bound to 0.0.0.0 or an accessible network interface rather than only localhost (127.0.0.1)Affected if DevTools debugging port is accessible from network interfaces other than localhost
-
Confirm active debugging sessionCheck if a remote debugging server is currently running - look for Chrome processes with debugging ports listening (e.g., via 'netstat -an | grep debug_port' or 'ss -tlnp | grep chrome')Affected if A Chrome remote debugging server is actively listening on a network-accessible port
User is affected if Chrome version is below 66.0.3359.117 AND remote DevTools debugging is enabled and accessible to untrusted networks.
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 data66.0.3359.117
Update Google Chrome to version 66.0.3359.117 or later. If remote DevTools debugging is enabled, restrict it to trusted networks or disable it if not needed.
Fix this in Linux Desktop
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6101 — 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-2018-6101 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