CVE-2017-14054
First published: Thu Aug 31 2017(Updated: )
In libavformat/rmdec.c in FFmpeg 3.3.3, a DoS in ivr_read_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted IVR file, which claims a large "len" field in the header but does not contain sufficient backing data, is provided, the first type==4 loop would consume huge CPU resources, since there is no EOF check inside the loop.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FFmpeg | =3.3.3 |
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-14054?
CVE-2017-14054 is classified as a denial of service (DoS) vulnerability due to excessive CPU consumption.
How do I fix CVE-2017-14054?
To fix CVE-2017-14054, upgrade to a patched version of FFmpeg beyond 3.3.3.
What software is affected by CVE-2017-14054?
CVE-2017-14054 affects FFmpeg version 3.3.3.
What is the impact of CVE-2017-14054?
The impact of CVE-2017-14054 is that it allows a crafted IVR file to cause huge CPU consumption.
How does CVE-2017-14054 exploit occur?
CVE-2017-14054 exploit occurs when an IVR file claims a large 'len' field but has insufficient backing data.
- agent/type
- agent/references
- agent/author
- agent/remedy
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/description
- 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/3.3.3