CVE-2017-7862: Buffer Overflow
First published: Fri Apr 14 2017(Updated: )
FFmpeg before 2017-02-07 has an out-of-bounds write caused by a heap-based buffer overflow related to the decode_frame function in libavcodec/pictordec.c.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FFmpeg | <=2.8.10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-7862?
CVE-2017-7862 has a high severity rating due to its potential for causing a denial of service or remote code execution.
How do I fix CVE-2017-7862?
To fix CVE-2017-7862, upgrade FFmpeg to version 2.8.11 or later.
What type of vulnerability is CVE-2017-7862?
CVE-2017-7862 is classified as a heap-based buffer overflow vulnerability.
Which versions of FFmpeg are affected by CVE-2017-7862?
FFmpeg versions prior to 2.8.11 are affected by CVE-2017-7862.
What component of FFmpeg does CVE-2017-7862 impact?
CVE-2017-7862 impacts the decode_frame function within libavcodec, specifically in pictordec.c.
- agent/references
- agent/remedy
- agent/weakness
- agent/severity
- agent/author
- agent/softwarecombine
- agent/description
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/ffmpeg
- canonical/ffmpeg
- version/ffmpeg/2.8.10