VulnerabilityModified
CVE-2017-14222
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.
MEDIUM 6.5EPSS 2.40%
Does this matter?
Lower severity and a low EPSS score (2.40%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.0
- 6.5 MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- EPSS
- 2.40% probability · 83th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-834
- Affected
- ffmpeg/ffmpeg
- Source
- cve@mitre.org
References
- http://www.debian.org/security/2017/dsa-3996
- http://www.securityfocus.com/bid/100701Third Party Advisory, VDB Entry
- https://github.com/FFmpeg/FFmpeg/commit/9cb4eb772839c5e1de2855d126bf74ff16d13382Issue Tracking, Patch, Third Party Advisory
- http://www.debian.org/security/2017/dsa-3996
- http://www.securityfocus.com/bid/100701Third Party Advisory, VDB Entry
- https://github.com/FFmpeg/FFmpeg/commit/9cb4eb772839c5e1de2855d126bf74ff16d13382Issue Tracking, Patch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.