dbcve.org
ChromeWeb browser · Google

CVE-2019-5775

MEDIUM · 6.5 CVSS v3.0 Published 2019-02-19
Fix available
A fix is available. Upgrade to 72.0.3626.81 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) 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 confidence

URL spoofing vulnerability in Google Chrome's Omnibox (address bar) where incorrect handling of confusable Unicode characters (homoglyphs) allows attackers to display a malicious domain as a trusted one, potentially tricking users into believing they're on a legitimate website.

MitigationUpgrade Google Chrome to version 72.0.3626.81 or later to patch the vulnerable character handling logic in the Omnibox.

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
Affected:< 72.0.3626.81
Debian LinuxOperating system
Affected:= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
FedoraOperating system
Affected:= 29= 30

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version on desktop
    Open Google Chrome, click the three-dot menu in the top-right, select 'Help', then 'About Google Chrome'. The version number is displayed on that page.
    Affected if The displayed version is lower than 72.0.3626.81 (for example, 71.0.3578.98 or any version in the 70.x or 71.x series).
  2. Check Chrome version via command line (if available)
    On systems with Chrome installed, run 'google-chrome --version' or 'google-chrome-stable --version' in a terminal to retrieve the installed version number.
    Affected if The command output shows a version lower than 72.0.3626.81.
  3. Check Chrome package version on Debian/Ubuntu
    If Chrome was installed via apt, run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to see the installed and available package versions.
    Affected if The installed version shown is lower than 72.0.3626.81.
  4. Check Chrome version on Red Hat/Fedora systems
    On RHEL or Fedora systems with Chrome installed, run 'rpm -qa | grep chrome' or 'yum list installed | grep chrome' to identify the installed Chrome package and its version.
    Affected if The listed package version is older than 72.0.3626.81.
  5. Verify homoglyph protection (if you can test URLs)
    Note that the vulnerability allows malicious domains using confusable Unicode characters (homoglyphs) to appear as trusted domains in the address bar. There is no simple config file to check; this is a logic flaw in character handling that is fixed by the version upgrade.
    Affected if Running an older Chrome version (below 72.0.3626.81) means the Omnibox may incorrectly display confusable Unicode domains as trusted.

You are affected if Google Chrome is installed and its version is lower than 72.0.3626.81, as only version 72.0.3626.81 and later contain the fix for the Omnibox homoglyph handling flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 72.0.3626.81 or later
Fixed in 72.0.3626.81
Interim mitigation

Upgrade Google Chrome to version 72.0.3626.81 or later to patch the vulnerable character handling logic in the Omnibox.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5775 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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