CVE-2017-5037: Integer Overflow
Published Apr 24, 2017
·Updated
An integer overflow in FFmpeg in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed a remote attacker to perform an out of bounds memory write via a crafted video file, related to ChunkDemuxer.
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
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5037?
CVE-2017-5037 has a severity rating classified as high due to its potential impact on system security.
2
How do I fix CVE-2017-5037?
To fix CVE-2017-5037, update Google Chrome to version 57.0.2987.98 or later.
3
Which versions of Google Chrome are affected by CVE-2017-5037?
Google Chrome versions prior to 57.0.2987.98 for Mac, Windows, and Linux are affected by CVE-2017-5037.
4
Can CVE-2017-5037 affect Android devices?
Yes, CVE-2017-5037 can affect Android devices running versions of Google Chrome prior to 57.0.2987.108.
5
Is the Linux Kernel vulnerable to CVE-2017-5037?
No, the Linux Kernel is not vulnerable to CVE-2017-5037.