ChromeWeb browser · Google
CVE-2018-16064
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 data validation in Extensions API in Google Chrome prior to 68.0.3440.75 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions 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 · moderate confidenceInsufficient data validation in Google Chrome's Extensions API allowed a malicious extension to bypass navigation restrictions. An attacker needed to convince a user to install a crafted extension, which could then exploit the validation flaw to perform unauthorized navigation actions.
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
< 68.0.3440.75CVSS 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.
-
Confirm Google Chrome is installedOn Windows, check for Chrome in Program Files or verify chrome.exe exists. On Mac, verify /Applications/Google Chrome exists. On Linux, check if google-chrome command is available in PATH.Affected if Google Chrome is present on the system
-
Determine installed Google Chrome versionNavigate to chrome://settings/help in the Chrome address bar to view the current version. Alternatively, run 'google-chrome --version' from command line on Linux/Mac, or right-click chrome.exe and select Properties > Details to see the File version on Windows.Affected if Version cannot be determined or Chrome is not accessible for checking
-
Compare version against the affected rangeCompare the installed version number to 68.0.3440.75. The affected range is any version lower than 68.0.3440.75 (for example, 68.0.3440.74, 67.x.x.x, 66.x.x.x, etc.).Affected if Installed version is less than 68.0.3440.75
-
Assess extension installation exposureCheck if users have permission to install Chrome extensions. In enterprise environments, review group policy settings for ExtensionInstallForcelist or ExtensionInstallWhitelist. Ask users if they have installed any extensions from sources other than the Chrome Web Store.Affected if Users can install arbitrary extensions and Chrome version is below 68.0.3440.75
You are affected if Google Chrome is installed with a version lower than 68.0.3440.75 and users can install or have installed untrusted extensions.
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 data68.0.3440.75
Update Google Chrome to version 68.0.3440.75 or later. Organizations should also implement extension whitelisting policies and restrict extension installation to trusted sources only.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16064 — 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-16064 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