CVE-2017-5049: Integer Overflow
Published Apr 25, 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
12 affected components
Google Chrome<=57.0.2987.75
Apple macOS
Linux Linux kernel
Microsoft Windows
Google Chrome<=57.0.2987.100
Google Android
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 25, 2017
CVE Published
via MITRE·03:23 AM
Data Sourced
via MITRE·03:23 AM
DescriptionWeakness
Data Sourced
via NVD·03:59 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5049?
CVE-2017-5049 has been classified as a high severity vulnerability due to its potential to allow remote code execution.
2
How do I fix CVE-2017-5049?
To fix CVE-2017-5049, users should update Google Chrome to version 57.0.2987.98 or later.
3
What impact does CVE-2017-5049 have on my system?
CVE-2017-5049 can allow an attacker to write to memory out of bounds, potentially leading to crashes or code execution.
4
Which versions of Google Chrome are affected by CVE-2017-5049?
CVE-2017-5049 affects Google Chrome versions prior to 57.0.2987.98.
5
Is CVE-2017-5049 related to any specific components in Google Chrome?
CVE-2017-5049 is related to an integer overflow in the FFmpeg component of Google Chrome.