Linux DesktopOperating system · Redhat
CVE-2018-6104
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 confusable characters in URL Formatter in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to perform domain spoofing via IDN homographs via a crafted domain name.
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 confidenceThe URL Formatter in Google Chrome prior to version 66.0.3359.117 incorrectly handled confusable Unicode characters (IDN homographs), allowing attackers to craft domains with characters that visually resemble legitimate ASCII characters (e.g., Cyrillic 'a' vs Latin 'a'), enabling domain spoofing attacks where users believe they are visiting a trusted site.
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
- 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.
-
Verify Google Chrome is installedOn Windows: Check for Chrome in Program Files or via registry. On Linux: Run 'which google-chrome' or check package manager. On macOS: Check /Applications for Google Chrome.appAffected if Chrome is installed on the system
-
Determine installed Chrome versionOpen Chrome, click menu > Help > About Google Chrome, or run 'google-chrome --version' from command line on Linux/macOS, or check registry key HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon\version on WindowsAffected if Version number is returned and is less than 66.0.3359.117
-
Check if IDN (Internationalized Domain Name) support is activeVisit an IDN test site or observe if Chrome displays Unicode domains in the address bar. This vulnerability applies when Chrome renders IDN domains.Affected if IDN domains are rendered and version is below 66.0.3359.117
-
For Red Hat/Debian systems, verify installed browser packageOn RHEL/CentOS: 'rpm -q google-chrome'. On Debian: 'dpkg -l | grep google-chrome' or 'apt list --installed | grep chrome'Affected if Chrome package version is present and less than 66.0.3359.117
If Google Chrome is installed with a version lower than 66.0.3359.117, the environment is vulnerable to IDN homograph domain spoofing attacks.
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 automatic updates are enabled or deploy the update via standard patch management processes.
Fix this in Linux Desktop
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6104 — 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-6104 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