What is the severity of CVE-2017-5010?

CVE-2017-5010 has a medium severity rating due to the potential for remote code execution via UXSS attacks.

How do I fix CVE-2017-5010?

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

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

CVE-2017-5010 affects Google Chrome versions prior to 56.0.2924.76 for desktop and 56.0.2924.87 for Android.

What kind of attack is possible with CVE-2017-5010?

CVE-2017-5010 allows remote attackers to inject arbitrary scripts or HTML through a crafted HTML page.

Is the Linux version of Google Chrome vulnerable to CVE-2017-5010?

Yes, the Linux version of Google Chrome prior to 56.0.2924.76 is vulnerable to CVE-2017-5010.

Vulnerability/
CVE-2017-5010

medium

6.1

CWE

17/2/2017

5/8/2024

CVE-2017-5010: XSS

First published: Fri Feb 17 2017(Updated: )

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, resolved promises in an inappropriate context, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
Google Chrome	<=55.0.2883.87

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5010?
CVE-2017-5010 has a medium severity rating due to the potential for remote code execution via UXSS attacks.
How do I fix CVE-2017-5010?
To fix CVE-2017-5010, upgrade Google Chrome to version 56.0.2924.76 or later.
Which versions of Google Chrome are affected by CVE-2017-5010?
CVE-2017-5010 affects Google Chrome versions prior to 56.0.2924.76 for desktop and 56.0.2924.87 for Android.
What kind of attack is possible with CVE-2017-5010?
CVE-2017-5010 allows remote attackers to inject arbitrary scripts or HTML through a crafted HTML page.
Is the Linux version of Google Chrome vulnerable to CVE-2017-5010?
Yes, the Linux version of Google Chrome prior to 56.0.2924.76 is vulnerable to CVE-2017-5010.

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

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-5010?
CVE-2017-5010 has a medium severity rating due to the potential for remote code execution via UXSS attacks.
How do I fix CVE-2017-5010?
To fix CVE-2017-5010, upgrade Google Chrome to version 56.0.2924.76 or later.
Which versions of Google Chrome are affected by CVE-2017-5010?
CVE-2017-5010 affects Google Chrome versions prior to 56.0.2924.76 for desktop and 56.0.2924.87 for Android.
What kind of attack is possible with CVE-2017-5010?
CVE-2017-5010 allows remote attackers to inject arbitrary scripts or HTML through a crafted HTML page.
Is the Linux version of Google Chrome vulnerable to CVE-2017-5010?
Yes, the Linux version of Google Chrome prior to 56.0.2924.76 is vulnerable to CVE-2017-5010.