Linux DesktopOperating system · Redhat
CVE-2018-6099
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 · uneditedA lack of CORS checks in Blink in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak limited cross-origin data 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 confidenceA CORS (Cross-Origin Resource Sharing) bypass existed in Chrome's Blink rendering engine where proper origin checks were not enforced, allowing a remote attacker hosting a crafted HTML page to make requests to other origins and exfiltrate limited sensitive data that should have been protected by CORS policies.
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
Linux DesktopOperating system
= 6.0
Linux ServerOperating system
= 6.0
Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 8.0= 9.0
ChromeWeb browser
< 66.0.3359.117CVSS 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 installed Google Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chromium --version' from command lineAffected if Version is lower than 66.0.3359.117
-
Check Chrome package version on Red Hat systemsRun 'rpm -qa | grep -i chrome' or 'rpm -qi google-chrome-stable' to query the installed Chrome package versionAffected if Installed Chrome package version is below 66.0.3359.117 on Red Hat Linux 6.0
-
Check Chrome package version on Debian systemsRun 'dpkg -l | grep -i chrome' or 'dpkg -s google-chrome-stable' to query the installed Chrome package versionAffected if Installed Chrome package version is below 66.0.3359.117 on Debian Linux 8.0 or 9.0
-
Verify browser is being used in a vulnerable contextConfirm that users are making cross-origin requests from web pages hosted in Chrome - the vulnerability allows bypass of CORS policies for such requestsAffected if Users process untrusted web content in an affected Chrome version and the application relies on CORS for access control
A user is affected if Google Chrome version 66.0.3359.117 or earlier is installed on Red Hat Linux 6.0 or Debian Linux 8.0/9.0, and users process web content that relies on CORS protections.
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 data66.0.3359.117
Update Google Chrome to version 66.0.3359.117 or later. Organizations should ensure browser update policies are in place and may consider deploying Content Security Policy headers as a defense-in-depth measure.
Fix this in Linux Desktop
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-6099 — 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-6099 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