ChromeWeb browser · Google
CVE-2018-6050
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 security UI in Omnibox in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) 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 was a UI spoofing vulnerability in Chrome's Omnibox (URL bar) that allowed a remote attacker to display a fraudulent URL while actually navigating to a different website. The flaw enabled phishing attacks by making users believe they were visiting a legitimate site when they were actually on a malicious page.
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
< 64.0.3282.119
Debian LinuxOperating system
= 8.0= 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 Chrome version on LinuxRun 'google-chrome --version' or 'chromium --version' in terminalAffected if Version is lower than 64.0.3282.119
-
Check Chrome version on WindowsNavigate to Chrome help menu > About Google Chrome, or run 'chrome.exe --version' from command promptAffected if Version is lower than 64.0.3282.119
-
Check installed Chrome package on Debian systemsRun 'dpkg -l | grep chrome' or check /usr/bin/google-chrome --versionAffected if Package version is present and lower than 64.0.3282.119
-
Check installed Chrome package on RHEL systemsRun 'rpm -qa | grep -i chrome' to list installed Chrome packagesAffected if Chrome package is installed with version lower than 64.0.3282.119
-
Identify if Debian 8 or 9 ships vulnerable ChromeOn Debian 8 or 9 systems, check if Chrome was installed from the Google repository and note the versionAffected if Debian 8.0 or 9.0 with Chrome version below 64.0.3282.119
-
Identify if RHEL 6 ships vulnerable ChromeOn RHEL 6 systems, check if Chrome was installed and note the version from rpm packageAffected if RHEL 6 Desktop/Server/Workstation with Chrome version below 64.0.3282.119
User is affected if Google Chrome or Chromium browser is installed and its version is below 64.0.3282.119, particularly on Debian 8/9 or RHEL 6 systems.
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 data64.0.3282.119
Update Google Chrome to version 64.0.3282.119 or later to patch the vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6050 — 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-6050 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