In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.
References
Link | Resource |
---|---|
http://www.debian.org/security/2017/dsa-3996 | |
http://www.securityfocus.com/bid/100701 | Third Party Advisory VDB Entry |
https://github.com/FFmpeg/FFmpeg/commit/9cb4eb772839c5e1de2855d126bf74ff16d13382 | Issue Tracking Patch Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2017-09-09T01:00:00
Updated: 2017-11-03T18:57:01
Reserved: 2017-09-08T00:00:00
Link: CVE-2017-14222
JSON object: View
NVD Information
Status : Modified
Published: 2017-09-09T01:29:02.737
Modified: 2019-10-03T00:03:26.223
Link: CVE-2017-14222
JSON object: View
Redhat Information
No data.
CWE