Filtered by vendor Ffmpeg
Subscribe
Total
420 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2009-0385 | 4 Canonical, Debian, Fedoraproject and 1 more | 4 Ubuntu Linux, Debian Linux, Fedora and 1 more | 2020-11-20 | 9.3 HIGH | N/A |
Integer signedness error in the fourxm_read_header function in libavformat/4xm.c in FFmpeg before revision 16846 allows remote attackers to execute arbitrary code via a malformed 4X movie file with a large current_track value, which triggers a NULL pointer dereference. | |||||
CVE-2020-14212 | 1 Ffmpeg | 1 Ffmpeg | 2020-09-18 | 6.8 MEDIUM | 8.8 HIGH |
FFmpeg through 4.3 has a heap-based buffer overflow in avio_get_str in libavformat/aviobuf.c because dnn_backend_native.c calls ff_dnn_load_model_native and a certain index check is omitted. | |||||
CVE-2019-12730 | 1 Ffmpeg | 1 Ffmpeg | 2020-08-24 | 7.5 HIGH | 9.8 CRITICAL |
aa_read_header in libavformat/aadec.c in FFmpeg before 3.2.14 and 4.x before 4.1.4 does not check for sscanf failure and consequently allows use of uninitialized variables. | |||||
CVE-2019-13312 | 1 Ffmpeg | 1 Ffmpeg | 2020-07-28 | 6.8 MEDIUM | 8.8 HIGH |
block_cmp() in libavcodec/zmbvenc.c in FFmpeg 4.1.3 has a heap-based buffer over-read. | |||||
CVE-2019-13390 | 1 Ffmpeg | 1 Ffmpeg | 2020-07-27 | 4.3 MEDIUM | 6.5 MEDIUM |
In FFmpeg 4.1.3, there is a division by zero at adx_write_trailer in libavformat/rawenc.c. | |||||
CVE-2018-6912 | 1 Ffmpeg | 1 Ffmpeg | 2020-03-30 | 4.3 MEDIUM | 6.5 MEDIUM |
The decode_plane function in libavcodec/utvideodec.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (out of array read) via a crafted AVI file. | |||||
CVE-2018-7751 | 1 Ffmpeg | 1 Ffmpeg | 2020-03-30 | 4.3 MEDIUM | 6.5 MEDIUM |
The svg_probe function in libavformat/img2dec.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (Infinite Loop) via a crafted XML file. | |||||
CVE-2018-9841 | 1 Ffmpeg | 1 Ffmpeg | 2020-03-30 | 6.8 MEDIUM | 8.8 HIGH |
The export function in libavfilter/vf_signature.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (out-of-array access) or possibly have unspecified other impact via a long filename. | |||||
CVE-2018-10001 | 2 Debian, Ffmpeg | 2 Debian Linux, Ffmpeg | 2020-03-30 | 4.3 MEDIUM | 6.5 MEDIUM |
The decode_init function in libavcodec/utvideodec.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (out of array read) via an AVI file. | |||||
CVE-2014-4610 | 1 Ffmpeg | 1 Ffmpeg | 2020-01-21 | 6.8 MEDIUM | 8.8 HIGH |
Integer overflow in the get_len function in libavutil/lzo.c in FFmpeg before 0.10.14, 1.1.x before 1.1.12, 1.2.x before 1.2.7, 2.0.x before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.4 allows remote attackers to execute arbitrary code via a crafted Literal Run. | |||||
CVE-2018-13305 | 1 Ffmpeg | 1 Ffmpeg | 2020-01-13 | 5.8 MEDIUM | 8.1 HIGH |
In FFmpeg 4.0.1, due to a missing check for negative values of the mquant variable, the vc1_put_blocks_clamped function in libavcodec/vc1_block.c may trigger an out-of-array access while converting a crafted AVI file to MPEG4, leading to an information disclosure or a denial of service. | |||||
CVE-2017-14055 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
In libavformat/mvdec.c in FFmpeg 3.3.3, a DoS in mv_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MV file, which claims a large "nb_frames" field in the header but does not contain sufficient backing data, is provided, the loop over the frames would consume huge CPU and memory resources, since there is no EOF check inside the loop. | |||||
CVE-2017-14059 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large "duration" field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop. | |||||
CVE-2017-14054 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
In libavformat/rmdec.c in FFmpeg 3.3.3, a DoS in ivr_read_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted IVR file, which claims a large "len" field in the header but does not contain sufficient backing data, is provided, the first type==4 loop would consume huge CPU resources, since there is no EOF check inside the loop. | |||||
CVE-2017-14056 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops. | |||||
CVE-2018-13304 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 4.3 MEDIUM | 6.5 MEDIUM |
In libavcodec in FFmpeg 4.0.1, improper maintenance of the consistency between the context profile field and studio_profile in libavcodec may trigger an assertion failure while converting a crafted AVI file to MPEG4, leading to a denial of service, related to error_resilience.c, h263dec.c, and mpeg4videodec.c. | |||||
CVE-2017-14057 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
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. | |||||
CVE-2018-13302 | 2 Debian, Ffmpeg | 2 Debian Linux, Ffmpeg | 2019-10-02 | 6.8 MEDIUM | 8.8 HIGH |
In FFmpeg 4.0.1, improper handling of frame types (other than EAC3_FRAME_TYPE_INDEPENDENT) that have multiple independent substreams in the handle_eac3 function in libavformat/movenc.c may trigger an out-of-array access while converting a crafted AVI file to MPEG4, leading to a denial of service or possibly unspecified other impact. | |||||
CVE-2018-1999012 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
FFmpeg before commit 9807d3976be0e92e4ece3b4b1701be894cd7c2e1 contains a CWE-835: Infinite loop vulnerability in pva format demuxer that can result in a Vulnerability that allows attackers to consume excessive amount of resources like CPU and RAM. This attack appear to be exploitable via specially crafted PVA file has to be provided as input. This vulnerability appears to have been fixed in 9807d3976be0e92e4ece3b4b1701be894cd7c2e1 and later. | |||||
CVE-2017-14222 | 1 Ffmpeg | 1 Ffmpeg | 2019-10-02 | 7.1 HIGH | 6.5 MEDIUM |
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. |