dbcve.org
ChromeWeb browser · Google

CVE-2019-5801

MEDIUM · 6.5 CVSS v3.1 Published 2019-05-23
Fix available
A fix is available. Upgrade to 73.0.3683.75 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 eliding of URLs in Omnibox in Google Chrome on iOS prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing 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 confidence

A vulnerability in Google Chrome's Omnibox (address bar) on iOS allowed incorrect URL eliding (truncation/abbreviation), which could be exploited to perform domain spoofing. A remote attacker could craft a malicious HTML page to manipulate how URLs are displayed in the address bar, potentially deceiving users about the true domain they are visiting.

MitigationUpdate Google Chrome for iOS to version 73.0.3683.75 or later to receive the fix for incorrect URL eliding 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:< 73.0.3683.75
BackportsOperating system
Affected:= sle-15
LeapOperating system
Affected:= 15.0= 15.1= 42.3

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.1/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. Identify Google Chrome for iOS installation
    On the iOS device, go to Settings > Chrome or check the App Library to confirm Google Chrome for iOS is installed
    Affected if Google Chrome for iOS is present on the device
  2. Check installed Chrome for iOS version
    Open Google Chrome for iOS, tap the three dots menu, go to Settings, scroll to and tap Chrome to view the version number
    Affected if The displayed version is below 73.0.3683.75
  3. Confirm vulnerability trigger condition
    The vulnerability requires a user to visit a maliciously crafted HTML page that exploits incorrect URL eliding (truncation) in the address bar. This is a client-side UI spoofing issue that manifests during browsing.
    Affected if An affected version of Chrome for iOS is used AND the user visits a malicious page designed to exploit URL eliding behavior in the Omnibox

The user is affected if Google Chrome for iOS with version less than 73.0.3683.75 is installed and the browser is used to navigate to web content, as the vulnerability is triggered when visiting specially crafted HTML pages that manipulate URL display in the address bar.

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 73.0.3683.75 or later
Fixed in 73.0.3683.75
Interim mitigation

Update Google Chrome for iOS to version 73.0.3683.75 or later to receive the fix for incorrect URL eliding 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-5801 — 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-5801 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