dbcve.org
ChromeWeb browser · Google

CVE-2018-6147

MEDIUM · 5.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 67.0.3396.62 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Lack of secure text entry mode in Browser UI in Google Chrome on Mac prior to 67.0.3396.62 allowed a local attacker to obtain potentially sensitive information from process memory via a local process.

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

A vulnerability in Google Chrome on Mac versions prior to 67.0.3396.62 allowed a local attacker to access potentially sensitive information from process memory due to missing secure text entry mode protections in the Browser UI. This is a local information disclosure issue requiring a malicious local process.

MitigationUpdate Google Chrome to version 67.0.3396.62 or later to obtain the secure text entry mode fix.

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:< 67.0.3396.62
Debian LinuxOperating system
Affected:= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check if Google Chrome is installed
    Open terminal and run: which google-chrome or ls /Applications/Google\ Chrome.app (Mac) or locate the chrome executable
    Affected if Google Chrome is found on the system
  2. Determine installed Chrome version on Mac/Linux
    Run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (Mac) or google-chrome --version (Linux)
    Affected if Version is lower than 67.0.3396.62
  3. Check OS version on Debian Linux
    Run: cat /etc/debian_version
    Affected if Version equals 9.0 and Chrome is installed
  4. Check OS version on Red Hat Enterprise Linux
    Run: cat /etc/redhat-release
    Affected if Version shows 6.0 (Desktop, Server, or Workstation) and Chrome is installed

The system is affected if Google Chrome version is below 67.0.3396.62 on Mac, or if Chrome is installed on Debian 9.0 or RHEL 6.0 systems running a vulnerable Chrome version.

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 67.0.3396.62 or later
Fixed in 67.0.3396.62
Interim mitigation

Update Google Chrome to version 67.0.3396.62 or later to obtain the secure text entry mode fix.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6147 — 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-2018-6147 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