dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2024-57510

HIGH · 7.8 CVSS v3.1 Published 2025-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer Overflow vulnerability in Bento4 mp42avc v.3bdc891602d19789b8e8626e4a3e613a937b4d35 allows a local attacker to execute arbitrary code via the AP4_MemoryByteStream::WritePartial.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in Bento4's mp42avc tool in the AP4_MemoryByteStream::WritePartial function allows a local attacker to write beyond buffer boundaries and execute arbitrary code.

MitigationUpdate Bento4 to a patched version after the vulnerable commit (3bdc8916) that includes proper bounds checking in AP4_MemoryByteStream::WritePartial; alternatively, implement input validation on write sizes before calling WritePartial.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Bento4 mp42avc tool is installed
    Locate the mp42avc binary on the system using 'which mp42avc' or search in common installation directories (/usr/bin, /usr/local/bin, or via package manager listings)
    Affected if The mp42avc binary exists on the system
  2. Identify the installed Bento4 version
    Run 'mp42avc --version' or check package metadata if installed via a package manager (dpkg, rpm, brew)
    Affected if Unable to determine version or version is older than the patched commit 3bdc8916
  3. Verify the source code commit if building from source
    If Bento4 was built from source, check the git log for the commit hash in the repository: 'git log --oneline -1' in the source directory
    Affected if The repository commit precedes 3bdc8916 (the vulnerable commit)
  4. Confirm the vulnerable function is reachable
    Review if mp42avc processes input files (AVC video streams) that trigger the AP4_MemoryByteStream::WritePartial function during normal operation
    Affected if mp42avc is used to process video files - the buffer overflow occurs during write operations in this tool

A system is affected if Bento4's mp42avc tool is installed and the version (or source commit) predates the patched commit 3bdc8916.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Bento4 to a patched version after the vulnerable commit (3bdc8916) that includes proper bounds checking in AP4_MemoryByteStream::WritePartial; alternatively, implement input validation on write sizes before calling WritePartial.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57510 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data