ChromeWeb browser · Google
CVE-2018-6133
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 67.0.3396.62 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 67.0.3396.62 incorrectly handled confusable characters in Internationalized Domain Names (IDN), allowing attackers to use homograph characters from different scripts that visually resemble legitimate characters to perform domain spoofing.
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
< 67.0.3396.62
Debian LinuxOperating system
= 9.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.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
- 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.
-
Check if Google Chrome is installedWindows: Look in C:\Program Files\Google\Chrome\Application\ or check Add/Remove Programs. Linux: Run 'which google-chrome' or 'dpkg -l | grep chrome' (Debian) or 'rpm -qa | grep chrome' (RHEL). macOS: Check /Applications for Google Chrome.appAffected if Google Chrome browser is installed on the system
-
Determine the installed Chrome versionWindows: Open Chrome, go to Settings > About Chrome, or check the chrome.dll version in the install folder. Linux: Run 'google-chrome --version' or 'google-chrome-stable --version'. macOS: Right-click Google Chrome in Applications > Get InfoAffected if Unable to determine version or version is below 67.0.3396.62
-
Compare installed version against the vulnerable rangeIf version is found, compare numerically: any version less than 67.0.3396.62 is affected (e.g., 66.x.x.x, 65.x.x.x, etc.)Affected if Installed version is less than 67.0.3396.62
-
Verify IDN support is enabled (required for exploitation)In Chrome, go to Settings > Advanced > Privacy and security > Security and ensure 'Safe Browsing' or standard security settings are active. IDN display is enabled by default in ChromeAffected if IDN support is enabled (default state) and Chrome version is vulnerable
The environment is affected if Google Chrome is installed with a version lower than 67.0.3396.62 and IDN domains are accessible to the browser.
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 data67.0.3396.62
Update Google Chrome to version 67.0.3396.62 or later to remediate this vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-6133 — 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-6133 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