CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2017 · Ffmpeg

CVE-2017-14222
Ffmpeg vulnerability

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.

Affected products

Ffmpeg. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Ffmpeg runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Ffmpeg products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.