dbcve.org
ChromeWeb browser · Google

CVE-2019-5812

MEDIUM · 6.5 CVSS v3.1 Published 2019-06-27
Fix available
A fix is available. Upgrade to 74.0.3729.108 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
Inadequate security UI in iOS UI in Google Chrome prior to 74.0.3729.108 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 security UI flaw in Google Chrome on iOS before version 74.0.3729.108 allowed attackers to spoof domain names via malicious HTML pages, tricking users into believing they were on a legitimate site.

MitigationUpdate Google Chrome for iOS to version 74.0.3729.108 or later to remediate the domain spoofing vulnerability.

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:< 74.0.3729.108
FedoraOperating system
Affected:= 29

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. Confirm Google Chrome is installed on iOS
    Open the iOS device home screen and locate the Chrome app icon, or check Settings > General > iPhone Storage to verify Chrome is installed
    Affected if Google Chrome app is present on the iOS device
  2. Determine the installed Chrome version on iOS
    Open Chrome app, tap the three-dot menu, go to Settings, then scroll to the bottom to view the version number displayed as 'Chrome [version]'
    Affected if The displayed version is a number less than 74.0.3729.108 (for example, 73.x.x.x)
  3. Check iOS Chrome build number for precise version
    From the version screen in Chrome settings, note the full version string which includes both the version number and build number (format: XX.X.XXXXX.X)
    Affected if The build number is lower than 3729.108 when the major version is below 74

A user is affected if Google Chrome for iOS is installed and its version number is below 74.0.3729.108, meaning the UI domain spoofing vulnerability is present in their browser.

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

Update Google Chrome for iOS to version 74.0.3729.108 or later to remediate the domain spoofing vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5812 — 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-5812 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