In libavformat/mxfdec.c in FFmpeg 3.3.3 -> 2.4, a DoS in mxf_read_index_entry_array() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted MXF file, which claims a large "nb_index_entries" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU resources, since there is no EOF check inside the loop. Moreover, this big loop can be invoked multiple times if there is more than one applicable data segment in the crafted MXF file.
References
Configurations
History
21 Nov 2024, 03:12
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.debian.org/security/2017/dsa-3996 - | |
References | () http://www.securityfocus.com/bid/100700 - | |
References | () https://github.com/FFmpeg/FFmpeg/commit/900f39692ca0337a98a7cf047e4e2611071810c2 - Issue Tracking, Patch, Third Party Advisory | |
References | () https://github.com/FFmpeg/FFmpeg/commit/f173cdfe669556aa92857adafe60cbe5f2aa1210 - | |
References | () https://lists.debian.org/debian-lts-announce/2019/01/msg00006.html - |
Information
Published : 2017-09-07 06:29
Updated : 2024-11-21 03:12
NVD link : CVE-2017-14170
Mitre link : CVE-2017-14170
CVE.ORG link : CVE-2017-14170
JSON object : View
Products Affected
ffmpeg
- ffmpeg
CWE
CWE-834
Excessive Iteration