CVE-2017-14222

Name: CVE-2017-14222
Creator: NVD / NIST
Published: 2017-09-09T01:29:02.737+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.40%

Last modified Jun 17, 2026

CVE-2017-14222 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.40% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

2.40%

81.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-834

Affected Software

Vendor	Product	Versions
Ffmpeg	Ffmpeg	3.3.3

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

Timeline

Published: Sep 9, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-14222?

How severe is CVE-2017-14222?

Severity scoring for CVE-2017-14222 is pending analysis. The EPSS model estimates a 2.40% probability of exploitation in the next 30 days.

How do I fix CVE-2017-14222?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-14222?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST