dbcve.org
ChromeWeb browser · Google

CVE-2018-6127

CRITICAL · 9.6 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 67.0.3396.62 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Early free of object in use in IndexDB in Google Chrome prior to 67.0.3396.62 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.

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

Use-after-free vulnerability in Chrome's IndexDB implementation where an object was freed while still in use. A remote attacker with a compromised renderer process could exploit this via crafted HTML to potentially escape the Chrome sandbox and execute code on the underlying system.

MitigationUpdate Google Chrome to version 67.0.3396.62 or later. This is a browser vulnerability requiring client-side patching; web application mitigations are limited to advising users to update.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux) or 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' (Windows)
    Affected if Version is lower than 67.0.3396.62
  2. Check Chrome package version on Debian 9.0
    Run 'dpkg -l | grep google-chrome' or 'apt policy google-chrome-stable'
    Affected if Installed version is less than 67.0.3396.62 on Debian 9.0
  3. Check Chrome version on RHEL 6.0 desktop or workstation
    Run 'rpm -qa | grep chrome' or check the installed package version via yum
    Affected if Chrome version is less than 67.0.3396.62 on RHEL 6.0 systems
  4. Verify IndexDB API is enabled (default state)
    In Chrome, navigate to chrome://flags and search for 'IndexedDB' or 'IndexedDB' settings; confirm it is not disabled
    Affected if IndexDB has been manually disabled, though this is uncommon and would only prevent exploitation, not confirm safety

You are affected if Google Chrome version is below 67.0.3396.62, regardless of OS, as this is a browser renderer vulnerability that applies to any Chrome installation on the listed versions.

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.

dbcve · scoped
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. This is a browser vulnerability requiring client-side patching; web application mitigations are limited to advising users to update.

Recommended fix High confidence

Chrome 67.0.3396.62 or later (stable release)

  1. Check current Google Chrome version by navigating to chrome://settings/help or using 'Google Chrome' > 'About Google Chrome'
  2. Update Google Chrome to version 67.0.3396.62 or later. This can be done automatically via the built-in updater or by downloading the latest version from the official Chrome download page
  3. After the update is installed, restart Google Chrome to apply the fix
  4. Verify the fix by checking chrome://settings/help to confirm the installed version is 67.0.3396.62 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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