CVE-2017-5024: Buffer Overflow
Published Feb 17, 2017
·Updated
FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file.
Affected Software
1 affected component
Google Chrome<=55.0.2883.87
Event History
Feb 17, 2017
CVE Published
via MITRE·07:45 AM
Data Sourced
via MITRE·07:45 AM
DescriptionWeakness
Data Sourced
via NVD·07:59 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5024?
CVE-2017-5024 has a medium severity rating due to the potential for remote exploitation leading to heap corruption.
2
How do I fix CVE-2017-5024?
To fix CVE-2017-5024, update Google Chrome to version 56.0.2924.76 or later.
3
What versions of Google Chrome are affected by CVE-2017-5024?
CVE-2017-5024 affects Google Chrome versions prior to 56.0.2924.76.
4
Can CVE-2017-5024 be exploited remotely?
Yes, CVE-2017-5024 can potentially be exploited remotely via a specially crafted video file.
5
What type of vulnerability is CVE-2017-5024?
CVE-2017-5024 is a heap corruption vulnerability resulting from improper bounds checking in FFmpeg.