RHEL 5 : qffmpeg (Unpatched Vulnerability)

The remote Redhat Enterprise Linux 5 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched. - qffmpeg: Invalid free in libavcodec/shorten.c due to invalid channel count CVE-2013-0873 - qffmpeg: out o...

Design/Logic Flaw

In libavcodec in FFmpeg 4.0.1, improper maintenance of the consistency between the context profile field and studioprofile in libavcodec may trigger an assertion failure while converting a crafted AVI file to MPEG4, leading to a denial of service, related to errorresilience.c, h263dec.c, and...

CVE-2018-13304

In FFmpeg 4.0.1, the vulnerability CVE-2018-13304 stems from improper maintenance of consistency between the context profile field and studio_profile in libavcodec. This can trigger an assertion failure during conversion of a crafted AVI file to MPEG-4, potentially causing a denial of service. Af...

CVE-2011-3941

The decodemb function in libavcodec/errorresilience.c in FFmpeg before 0.10 allows remote attackers to have an unspecified impact via vectors related to an uninitialized block index, which triggers an out-of-bounds write...

Out-of-bounds

The decodemb function in libavcodec/errorresilience.c in FFmpeg before 0.10 allows remote attackers to have an unspecified impact via vectors related to an uninitialized block index, which triggers an out-of-bounds write...

CVE-2011-3941

FFmpeg vulnerability CVE-2011-3941: The decode_mb function in libavcodec/error_resilience.c enables an out-of-bounds write due to an uninitialized block index in FFmpeg before version 0.10. The issue is triggered by processing certain streams, with the CVE description noting an unspecified impact...

CVE-2013-0860

The CVE-2013-0860 vulnerability affects FFmpeg (libavcodec) where ff_er_frame_end in error_resilience.c can fail to verify frame initialization, allowing a remote attacker to trigger a NULL pointer dereference via crafted picture data. Public details indicate the issue exists in FFmpeg before 1.0...