ChromeWeb browser · Google
CVE-2018-6040
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 policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially bypass content security policy 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 confidenceInsufficient policy enforcement in Blink (Chrome's rendering engine) allowed a remote attacker to potentially bypass Content Security Policy (CSP) via a crafted HTML page. CSP is a critical security control that helps prevent XSS and data injection attacks by restricting resource loading; a bypass could enable script injection or unauthorized content loading.
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
< 64.0.3282.119
Debian LinuxOperating system
= 8.0= 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://version in the Chrome address bar or open Chrome, click the three-dot menu, select Help, then About Google Chrome. Note the version number displayed.Affected if The version displayed is lower than 64.0.3282.119 (e.g., 63.x.x.x or earlier)
-
Confirm Chrome is the browser in useVerify that the browser where CSP policies would be enforced is Google Chrome and not another Chromium-based browser, as the fix was applied specifically to Google Chrome.Affected if Google Chrome is in use and the version is vulnerable as above
-
Identify if Content Security Policy is deployedReview web application headers by using browser developer tools (F12), checking the Network tab for response headers, or using curl -I against the protected site to see if CSP headers (Content-Security-Policy) are present.Affected if CSP headers are actively configured and the Chrome version is vulnerable, meaning the bypass could be exploited
You are affected if you use Google Chrome version below 64.0.3282.119 and have Content Security Policy headers configured on your web applications, as the vulnerability allows bypassing those CSP controls.
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 data64.0.3282.119
Update Google Chrome to version 64.0.3282.119 or later to patch the Blink rendering engine. Additionally, ensure CSP policies are configured with strict default-src directives and avoid relying solely on browser-side enforcement for security-critical policies.
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-6040 — 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-6040 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