ChromeWeb browser · Google
CVE-2018-18351
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 · uneditedLack of proper validation of ancestor frames site when sending lax cookies in Navigation in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to bypass SameSite cookie 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 confidenceThis is a SameSite cookie bypass vulnerability in Google Chrome where improper validation of ancestor frames during navigation allowed attackers to send lax cookies in a way that circumvented the SameSite cookie policy, potentially enabling CSRF attacks.
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
< 71.0.3578.80
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedOn Windows: Check for Chrome in Program Files or via registry. On Linux: Check for /usr/bin/google-chrome or /opt/google/chrome/chrome. On macOS: Check /Applications/Google Chrome.appAffected if Chrome is not installed - the vulnerability does not apply
-
Determine the installed Chrome versionOpen Chrome, click menu > Help > About Google Chrome, or run 'google-chrome --version' in terminal, or check the executable's propertiesAffected if Version cannot be determined or is lower than 71.0.3578.80 - the browser is affected
-
Compare version against the vulnerable rangeCompare the installed version number to 71.0.3578.80 using standard version comparisonAffected if Installed version is less than 71.0.3578.80 - the SameSite cookie bypass vulnerability is present
-
Verify SameSite cookie behavior (optional confirmation)Inspect cookie headers in browser developer tools (F12 > Network tab) when navigating between frames on different origins. Look for lax cookies being sent in cross-site contexts where they should be blockedAffected if Lax cookies are being sent in contexts that SameSite=lax should block - confirms active exploitation of this bypass
A user is affected if Google Chrome version 71.0.3578.80 or higher is not installed, as versions below this contain the SameSite cookie validation flaw that allows CSRF bypass.
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 data71.0.3578.80
Update Google Chrome to version 71.0.3578.80 or later to receive the patch. Organizations should deploy the browser update through their standard patch management processes.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18351 — 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-18351 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