What is the severity of CVE-2017-5028?

CVE-2017-5028 has been classified as a high severity vulnerability due to its potential for cross-origin data leakage.

How do I fix CVE-2017-5028?

To fix CVE-2017-5028, upgrade Google Chrome to version 56.0.2924.76 or later.

What type of attack does CVE-2017-5028 enable?

CVE-2017-5028 enables attackers to leak cross-origin data through a crafted HTML page.

Which versions of Google Chrome are affected by CVE-2017-5028?

CVE-2017-5028 affects Google Chrome versions prior to 56.0.2924.76.

What component of Google Chrome is impacted by CVE-2017-5028?

CVE-2017-5028 impacts the V8 JavaScript engine within Google Chrome.

Vulnerability/
CVE-2017-5028

medium

6.5

CWE

25/1/2017

27/6/2019

5/8/2024

CVE-2017-5028: Input Validation

First published: Wed Jan 25 2017(Updated: )

Insufficient data validation in V8 in Google Chrome prior to 56.0.2924.76 allowed a remote attacker to leak cross-origin data via a crafted HTML page.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
Google Chrome	<56.0.2924.76
Google Chrome	<56.0.2924.76	56.0.2924.76

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

5931754691533737707

Peer vulnerabilities

(Found alongside the following vulnerabilities)

Frequently Asked Questions

What is the severity of CVE-2017-5028?
CVE-2017-5028 has been classified as a high severity vulnerability due to its potential for cross-origin data leakage.
How do I fix CVE-2017-5028?
To fix CVE-2017-5028, upgrade Google Chrome to version 56.0.2924.76 or later.
What type of attack does CVE-2017-5028 enable?
CVE-2017-5028 enables attackers to leak cross-origin data through a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2017-5028?
CVE-2017-5028 affects Google Chrome versions prior to 56.0.2924.76.
What component of Google Chrome is impacted by CVE-2017-5028?
CVE-2017-5028 impacts the V8 JavaScript engine within Google Chrome.

agent/references
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/severity
agent/weakness
agent/author
agent/description
collector/chrome-releases
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/google
canonical/google chrome

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-2017-5028?
CVE-2017-5028 has been classified as a high severity vulnerability due to its potential for cross-origin data leakage.
How do I fix CVE-2017-5028?
To fix CVE-2017-5028, upgrade Google Chrome to version 56.0.2924.76 or later.
What type of attack does CVE-2017-5028 enable?
CVE-2017-5028 enables attackers to leak cross-origin data through a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2017-5028?
CVE-2017-5028 affects Google Chrome versions prior to 56.0.2924.76.
What component of Google Chrome is impacted by CVE-2017-5028?
CVE-2017-5028 impacts the V8 JavaScript engine within Google Chrome.