ChromeWeb browser · Google
CVE-2019-5794
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 cancelled requests in Navigation in Google Chrome 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 confidenceA domain spoofing vulnerability in Google Chrome's navigation handling allowed attackers to misrepresent the true origin of a page by exploiting incorrect processing of cancelled network requests. The flaw enabled malicious HTML pages to display spoofed domain information in the browser's address bar, potentially tricking users into trusting fraudulent sites.
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
< 73.0.3683.75= 15.0= 15.0= 15.1= 42.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedOn Linux: check for /usr/bin/google-chrome or /opt/google/chrome/google-chrome. On Windows: check Program Files\Google\Chrome\Application\chrome.exe. On macOS: check /Applications/Google Chrome.appAffected if Google Chrome executable is not found on the system
-
Determine installed Chrome version via command lineRun 'google-chrome --version' on Linux, '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' on Windows, or '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' on macOSAffected if The command fails or Chrome is not installed
-
Compare version against the vulnerable thresholdParse the version number from step 2 and compare it to 73.0.3683.75 - the vulnerability affects versions below this thresholdAffected if Installed version is less than 73.0.3683.75 (for example, 73.0.3683.74 or earlier)
-
Check for openSUSE package installations (if applicable)On openSUSE systems, run 'rpm -qa | grep -i chrome' to list installed Chrome packages, or check via 'zypper se google-chrome'Affected if Chrome packages from openSUSE 15.0, 15.1, or 42.3 repositories are installed
The environment is affected if Google Chrome is installed and the version is below 73.0.3683.75, or if Chrome packages from the listed openSUSE versions are installed.
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 data73.0.3683.75
Update Google Chrome to version 73.0.3683.75 or later. Organizations should deploy browser updates through their patch management systems and verify completion across all endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5794 — 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-2019-5794 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