dbcve.org
ChromeWeb browser · Google

CVE-2018-6152

CRITICAL · 9.6 CVSS v3.0 Published 2018-12-04
Fix available
A fix is available. Upgrade to 66.0.3359.106 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
The implementation of the Page.downloadBehavior backend unconditionally marked downloaded files as safe, regardless of file type in Google Chrome prior to 66.0.3359.117 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted HTML page and user interaction.

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 · moderate confidence

In Google Chrome prior to 66.0.3359.117, the Page.downloadBehavior backend API unconditionally marked all downloaded files as safe regardless of actual file type. This allowed a malicious extension (requiring user installation) to potentially escape the browser sandbox through crafted HTML pages and user interaction.

MitigationUpdate Chrome to version 66.0.3359.117 or later. Review installed extensions and remove any untrusted or unknown extensions as the attack requires a malicious extension to be installed first.

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:< 66.0.3359.106
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Debian LinuxOperating system
Affected:= 9.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 Chrome version
    Navigate to chrome://settings/help or use 'About Google Chrome' menu option to view the installed version number
    Affected if Version is earlier than 66.0.3359.106 (e.g., 65.x.x.x or lower)
  2. Identify installed extensions
    Navigate to chrome://extensions/ and review all installed extensions. Click 'Developer mode' to see extension IDs and sources if needed
    Affected if Any untrusted, unknown, or suspiciously named extensions are present that you did not intentionally install
  3. Verify extension permissions
    For each extension in chrome://extensions/, click 'Details' and review permissions granted, particularly watch for broad permissions like 'Downloads', 'History', or 'TabCapture'
    Affected if Any extension has excessive or unnecessary permissions, especially to downloads or file system

You are affected if Chrome version is below 66.0.3359.106 AND a malicious extension with elevated permissions is installed, allowing the extension to exploit the unsafe file handling in downloads.

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

Update Chrome to version 66.0.3359.117 or later. Review installed extensions and remove any untrusted or unknown extensions as the attack requires a malicious extension to be installed first.

Recommended fix High confidence

Chrome 66.0.3359.117 or later (preferably latest stable)

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is earlier than 66.0.3359.117, click 'Update Google Chrome' to download and install the fixed version
  3. Restart Chrome to complete the update
  4. Alternatively, download the latest stable Chrome from official sources (chrome.com) and reinstall

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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