CVE-2024-31002: Bento4 · n/a
Affects Bento4Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubaxiomatic-systems/Bento4pkg:github/axiomatic-systems/Bento4Other threats | Affected
| 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 for official patches or updates from the Bento4 project and apply them immediately once available. 2. In the absence of patches, consider isolating or disabling vulnerable components that utilize the AP4 BitReader::ReadCache() function to reduce attack surface. 3. Employ network-level protections such as firewalls and intrusion detection/prevention systems (IDS/IPS) to detect and block suspicious traffic targeting media processing services. 4. Conduct thorough code audits and implement input validation and bounds checking in custom integrations of Bento4. 5. Use application-layer sandboxing or containerization to limit the impact of potential exploitation. 6. Monitor logs and network traffic for anomalies indicative of exploitation attempts. 7. Educate development and security teams about this vulnerability to ensure rapid response and remediation. 8. If feasible, restrict network exposure of services using Bento4 to trusted internal networks only.
Description
Buffer Overflow vulnerability in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the AP4 BitReader::ReadCache() at Ap4Utils.cpp component.