ChromeWeb browser · Google
CVE-2018-6139
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 target checks on the chrome.debugger API in DevTools in Google Chrome prior to 67.0.3396.62 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension.
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 confidenceThe chrome.debugger API in Google Chrome DevTools had insufficient target validation checks that allowed a malicious extension with the debugger permission to potentially access or control arbitrary contexts, leading to arbitrary code execution. The vulnerability stemmed from the API not properly validating debug targets before allowing debugger attachment.
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
< 67.0.3396.62
Debian LinuxOperating system
= 9.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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.
-
Verify Chrome browser versionNavigate to chrome://settings/help or run `google-chrome --version` in a terminal to determine the installed Chrome versionAffected if the installed version is earlier than 67.0.3396.62
-
Check for extensions with debugger permissionGo to chrome://extensions, enable Developer mode if needed, and inspect each extension's permissions. Specifically look for any extension listing the 'debugger' permissionAffected if an untrusted or unknown extension with debugger permission is installed and active
-
Verify Chrome on Debian 9On Debian systems, run `dpkg -l | grep -i chrom` or check the installed chromium/chrome package versionAffected if the system is Debian 9.0 and the Chrome package version is earlier than 67.0.3396.62
-
Verify Chrome on RHEL 6On Red Hat systems, run `rpm -qa | grep -i chrom` to check the installed Chrome/Chromium package versionAffected if the system is RHEL 6.0 (Desktop, Server, or Workstation) and the Chrome package version is earlier than 67.0.3396.62
You are affected if you are running Google Chrome version earlier than 67.0.3396.62 on any platform, or running Chrome on Debian 9.0 or RHEL 6.0 at the affected versions, particularly if you have untrusted extensions with debugger permission installed.
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 data67.0.3396.62
Update Google Chrome to version 67.0.3396.62 or later to receive the security fix. Additionally, users should avoid installing untrusted extensions and organizations should enforce extension allowlists.
Fix this in Chrome
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-6139 — 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-6139 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