CVE-2019-13718
First published: Mon Nov 25 2019(Updated: )
Insufficient data validation in Omnibox in Google Chrome prior to 78.0.3904.70 allowed a remote attacker to perform domain spoofing via IDN homographs via a crafted domain name.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <78.0.3904.70 | |
| openSUSE Backports | =15.0-sp1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-13718?
CVE-2019-13718 is rated as high severity due to the potential for domain spoofing.
How do I fix CVE-2019-13718?
To fix CVE-2019-13718, update Google Chrome to version 78.0.3904.70 or later.
What types of software are affected by CVE-2019-13718?
CVE-2019-13718 affects Google Chrome prior to version 78.0.3904.70 and openSUSE Backports version 15.0-sp1.
What is the impact of CVE-2019-13718 on users?
CVE-2019-13718 allows attackers to execute domain spoofing attacks, potentially deceiving users into visiting malicious sites.
How can I determine if I'm vulnerable to CVE-2019-13718?
You can determine if you're vulnerable to CVE-2019-13718 by checking if you are using an outdated version of Google Chrome prior to 78.0.3904.70.
- agent/type
- agent/severity
- agent/references
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- vendor/google
- canonical/google chrome (trace event)
- vendor/opensuse
- canonical/opensuse backports
- version/opensuse backports/15.0-sp1