In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large "name_len" or "count" field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.
Advisories
Source ID Title
Debian DLA Debian DLA DLA-1630-1 libav security update
Debian DSA Debian DSA DSA-3996-1 ffmpeg security update
EUVD EUVD EUVD-2017-5571 In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large "name_len" or "count" field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T19:13:41.757Z

Reserved: 2017-08-31T00:00:00

Link: CVE-2017-14057

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-08-31T15:29:00.420

Modified: 2025-04-20T01:37:25.860

Link: CVE-2017-14057

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.