Skip to main content
VulnerabilityPublished Updated

CVE-2024-25452: Bento4 · Uncontrolled Resource Consumption

Affects Bento4Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Feb 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
GitHubaxiomatic-systems/Bento4pkg:github/axiomatic-systems/Bento4Other threatsAffected
  • =1.6.0-640
Fixed in–

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

AI-suggested

To mitigate CVE-2024-25452, organizations should implement the following specific measures: 1) Restrict access to systems running Bento4 to trusted users only, minimizing the risk of local exploitation. 2) Avoid processing untrusted or unauthenticated media files with vulnerable Bento4 versions. 3) Employ input validation and sanitization mechanisms upstream to detect and block malformed or suspicious media content before it reaches Bento4 processing. 4) Monitor system memory usage and application logs for signs of abnormal resource consumption or crashes related to media processing. 5) Implement resource limits (e.g., memory quotas, container limits) on Bento4 processes to prevent system-wide impact from out-of-memory conditions. 6) Stay alert for official patches or updates from Bento4 maintainers and apply them promptly once available. 7) Consider deploying runtime application self-protection (RASP) or endpoint detection solutions that can detect and block anomalous behavior during media parsing. These targeted mitigations go beyond generic advice by focusing on access control, input filtering, resource management, and proactive monitoring tailored to the nature of this vulnerability.

Description

Bento4 v1.6.0-640 was discovered to contain an out-of-memory bug via the AP4_UrlAtom::AP4_UrlAtom() function.

References

Community reviews

Loading reviews…