ChromeWeb browser · Google
CVE-2018-17468
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 · uneditedIncorrect handling of timer information during navigation in Blink in Google Chrome prior to 70.0.3538.67 allowed a remote attacker to obtain cross origin URLs 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 cross-origin information disclosure vulnerability in Chrome's Blink rendering engine. Incorrect handling of timer information during page navigation allows a remote attacker to discover URLs from other origins through crafted HTML pages exploiting timing side-channels.
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
< 70.0.3538.67
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 Google Chrome version on Windows/MacOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number displayed is the installed version.Affected if Version is lower than 70.0.3538.67
-
Check Google Chrome version on Linux via command lineRun 'google-chrome --version' or 'chrome --version' in terminal. Alternatively, navigate to chrome://settings/help in the browser.Affected if Version is lower than 70.0.3538.67
-
Check Chromium version on LinuxRun 'chromium --version' or 'chromium-browser --version' in terminal. Check the package version with 'dpkg -l | grep chromium' or 'rpm -qa | grep chromium'.Affected if Version is lower than 70.0.3538.67 or Chromium package version corresponds to a release before Chrome 70.0.3538.67
-
Check installed browsers on RHEL/CentOSRun 'rpm -qa | grep -i chrome' to list installed Google Chrome packages. Run 'rpm -qa | grep -i chromium' for Chromium.Affected if Any Chrome/Chromium package version is lower than 70.0.3538.67
-
Check installed browsers on Debian/UbuntuRun 'dpkg -l | grep -i chromium' or 'dpkg -l | grep -i google-chrome' to list installed browser packages. Use 'apt list --installed | grep -i chrome' as alternative.Affected if Any Chrome/Chromium package version is lower than 70.0.3538.67
A system is affected if Google Chrome, Chromium, or related browser packages are installed with a version number lower than 70.0.3538.67.
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 data70.0.3538.67
Update Google Chrome to version 70.0.3538.67 or later. Implement Content Security Policy (CSP) with 'frame-ancestors' directive and ensure proper CORS headers as defense-in-depth measures.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-17468 — 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-17468 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