What is the severity of CVE-2017-5009?

The severity of CVE-2017-5009 is classified as high due to its potential for remote code execution.

How do I fix CVE-2017-5009?

To fix CVE-2017-5009, users should update Google Chrome to version 56.0.2924.76 or later for Linux, Windows, and Mac, and version 56.0.2924.87 or later for Android.

What exploit is associated with CVE-2017-5009?

CVE-2017-5009 is associated with a heap corruption vulnerability that can be exploited using a crafted HTML page.

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

CVE-2017-5009 affects Google Chrome versions prior to 56.0.2924.76 for Linux, Windows, and Mac, and prior to 56.0.2924.87 for Android.

Who is impacted by CVE-2017-5009?

All users of affected Google Chrome versions on supported operating systems are potentially at risk from CVE-2017-5009.

Vulnerability/
CVE-2017-5009

high

8.8

CWE

119

17/2/2017

5/8/2024

CVE-2017-5009: Buffer Overflow

First published: Fri Feb 17 2017(Updated: )

WebRTC in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption 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-5009?
The severity of CVE-2017-5009 is classified as high due to its potential for remote code execution.
How do I fix CVE-2017-5009?
To fix CVE-2017-5009, users should update Google Chrome to version 56.0.2924.76 or later for Linux, Windows, and Mac, and version 56.0.2924.87 or later for Android.
What exploit is associated with CVE-2017-5009?
CVE-2017-5009 is associated with a heap corruption vulnerability that can be exploited using a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2017-5009?
CVE-2017-5009 affects Google Chrome versions prior to 56.0.2924.76 for Linux, Windows, and Mac, and prior to 56.0.2924.87 for Android.
Who is impacted by CVE-2017-5009?
All users of affected Google Chrome versions on supported operating systems are potentially at risk from CVE-2017-5009.

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-5009?
The severity of CVE-2017-5009 is classified as high due to its potential for remote code execution.
How do I fix CVE-2017-5009?
To fix CVE-2017-5009, users should update Google Chrome to version 56.0.2924.76 or later for Linux, Windows, and Mac, and version 56.0.2924.87 or later for Android.
What exploit is associated with CVE-2017-5009?
CVE-2017-5009 is associated with a heap corruption vulnerability that can be exploited using a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2017-5009?
CVE-2017-5009 affects Google Chrome versions prior to 56.0.2924.76 for Linux, Windows, and Mac, and prior to 56.0.2924.87 for Android.
Who is impacted by CVE-2017-5009?
All users of affected Google Chrome versions on supported operating systems are potentially at risk from CVE-2017-5009.