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.

Vulnerability/
CVE-2019-13718

medium

4.3

25/11/2019

5/8/2024

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	<78.0.3904.70
openSUSE Backports	=15.0-sp1

Never miss a vulnerability like this again

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/softwarecombine
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
vendor/google
canonical/google chrome
vendor/opensuse
canonical/opensuse backports
version/opensuse backports/15.0-sp1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.