What is the severity of CVE-2017-5017?

CVE-2017-5017 is considered a high severity vulnerability due to the potential for data leakage.

How do I fix CVE-2017-5017?

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

What are the impacted devices for CVE-2017-5017?

CVE-2017-5017 specifically affects Mac systems with GeForce 8600M graphics chips running vulnerable versions of Google Chrome.

What is the primary risk associated with CVE-2017-5017?

The primary risk associated with CVE-2017-5017 is that a remote attacker could extract sensitive image fragments from video memory.

How can I check if my version of Chrome is vulnerable to CVE-2017-5017?

You can check your version of Chrome by going to the 'About Google Chrome' section in the browser settings.

Vulnerability/
CVE-2017-5017

medium

4.3

CWE

200

17/2/2017

5/8/2024

CVE-2017-5017: Infoleak

First published: Fri Feb 17 2017(Updated: )

Interactions with the OS in Google Chrome prior to 56.0.2924.76 for Mac insufficiently cleared video memory, which allowed a remote attacker to possibly extract image fragments on systems with GeForce 8600M graphics chips 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-5017?
CVE-2017-5017 is considered a high severity vulnerability due to the potential for data leakage.
How do I fix CVE-2017-5017?
To fix CVE-2017-5017, upgrade Google Chrome to version 56.0.2924.76 or later.
What are the impacted devices for CVE-2017-5017?
CVE-2017-5017 specifically affects Mac systems with GeForce 8600M graphics chips running vulnerable versions of Google Chrome.
What is the primary risk associated with CVE-2017-5017?
The primary risk associated with CVE-2017-5017 is that a remote attacker could extract sensitive image fragments from video memory.
How can I check if my version of Chrome is vulnerable to CVE-2017-5017?
You can check your version of Chrome by going to the 'About Google Chrome' section in the browser settings.

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-5017?
CVE-2017-5017 is considered a high severity vulnerability due to the potential for data leakage.
How do I fix CVE-2017-5017?
To fix CVE-2017-5017, upgrade Google Chrome to version 56.0.2924.76 or later.
What are the impacted devices for CVE-2017-5017?
CVE-2017-5017 specifically affects Mac systems with GeForce 8600M graphics chips running vulnerable versions of Google Chrome.
What is the primary risk associated with CVE-2017-5017?
The primary risk associated with CVE-2017-5017 is that a remote attacker could extract sensitive image fragments from video memory.
How can I check if my version of Chrome is vulnerable to CVE-2017-5017?
You can check your version of Chrome by going to the 'About Google Chrome' section in the browser settings.