CVE-2017-5040: Medium severity Google Chrome vulnerability
Published Apr 24, 2017
·Updated
V8 in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android was missing a neutering check, which allowed a remote attacker to read values in memory via a crafted HTML page.
Affected Software
17 affected components
Google Chrome<=57.0.2987.75
Apple macOS
Linux Linux kernel
Microsoft Windows
Google Chrome<=57.0.2987.100
Google Android
Debian Debian Linux=8.0
Debian Debian Linux=9.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
All of the following
Google Chrome<=57.0.2987.75
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
All of the following
Google Chrome<=57.0.2987.100
Google Android
Remediation
Patch Available
Event History
Apr 24, 2017
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
DescriptionWeakness
Data Sourced
via NVD·11:59 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5040?
CVE-2017-5040 is rated as moderate in severity due to its ability to allow remote attackers to read memory values.
2
How do I fix CVE-2017-5040?
To fix CVE-2017-5040, update Google Chrome to version 57.0.2987.98 or later.
3
Which versions of Google Chrome are affected by CVE-2017-5040?
CVE-2017-5040 affects Google Chrome versions prior to 57.0.2987.98 for Mac, Windows, and Linux.
4
Can CVE-2017-5040 affect users on Android devices?
Yes, CVE-2017-5040 impacts Google Chrome on Android versions prior to 57.0.2987.108.
5
What is the nature of the vulnerability described in CVE-2017-5040?
CVE-2017-5040 is a memory vulnerability due to a missing neutering check in the V8 engine of Chrome.