Skip to main content
VulnerabilityPublished Updated

CVE-2024-31582: ffmpeg · Heap-based Buffer Overflow

Affects ffmpegSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubffmpeg/ffmpegpkg:github/ffmpeg/ffmpegOther threatsAffected
  • =6.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor FFmpeg project channels for official patches and apply them promptly once available. 2. Until patches are released, restrict processing of untrusted or unauthenticated media inputs, especially from external or unknown sources. 3. Implement sandboxing or containerization for applications using FFmpeg to limit the impact of potential exploitation. 4. Employ input validation and filtering to detect and block malformed or suspicious media files before processing. 5. Enhance user awareness and training to reduce the risk of social engineering attacks that could deliver crafted inputs. 6. Monitor logs and system behavior for signs of crashes or anomalous activity related to media processing components. 7. Review and update incident response plans to include scenarios involving media processing vulnerabilities. 8. Coordinate with software vendors and third-party providers to ensure they are aware of the vulnerability and their mitigation plans. 9. Consider network segmentation to isolate critical media processing infrastructure from general user environments. 10. Use application whitelisting and privilege restrictions to minimize the ability of exploited processes to cause broader system compromise.

Description

FFmpeg version n6.1 was discovered to contain a heap buffer overflow vulnerability in the draw_block_rectangle function of libavfilter/vf_codecview.c. This vulnerability allows attackers to cause undefined behavior or a Denial of Service (DoS) via crafted input.

References

Community reviews

Loading reviews…