Bento4Application

CVE-2017-14645

MEDIUM · 6.5 CVSS v3.0 Published 2017-09-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A heap-based buffer over-read was discovered in AP4_BitStream::ReadBytes in Codecs/Ap4BitStream.cpp in Bento4 version 1.5.0-617. The vulnerability causes an application crash, which leads to remote denial of service.

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

A heap-based buffer over-read vulnerability exists in the AP4_BitStream::ReadBytes function in Bento4 version 1.5.0-617. The vulnerability occurs when parsing specially crafted media files, allowing an attacker to read beyond allocated heap memory boundaries, causing an application crash and resulting in denial of service.

MitigationUsers should upgrade to a patched version of Bento4 or apply vendor-supplied patches. Until then, implement input validation to reject malformed MP4/media files before processing them with the vulnerable library.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bento4Application
Affected:= 1.5.0-617

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Identify if Bento4 is present in the environment
    Search for Bento4 binaries, libraries, or applications that use Bento4 code. Common binary names include 'mp4info', 'mp4extract', 'mp4dump', or look for libbento4 shared libraries. On Linux: `find /usr -name '*bento4*' 2>/dev/null` or `ldconfig -p | grep -i bento`. On Windows: search Program Files for bento4-related executables or DLLs.
    Affected if Bento4 software or libraries are found in the environment
  2. Determine the installed Bento4 version
    Run the bento4 utility with version flag: `mp4info --version` or `mp4extract --version`. If using as a library, check the shared library version or examine any version file included with the package. Compare the discovered version string against 1.5.0-617.
    Affected if The reported version is exactly 1.5.0-617
  3. Verify if media file processing is occurring
    Identify any applications, scripts, or services that parse MP4 or other media files using Bento4. Check for file upload functionality, media conversion pipelines, or automated processing of user-submitted content. Review application logs or configuration for media file handling.
    Affected if The environment processes MP4 or media files, especially from untrusted sources
  4. Check for vulnerable code path in custom builds
    If Bento4 is built from source or embedded in a custom application, examine the source code for the AP4_BitStream::ReadBytes function. Search for calls to ReadBytes that handle size parameters from untrusted input without proper bounds checking.
    Affected if Custom Bento4 code or embedded builds are in use and the ReadBytes function handles untrusted input

A user is affected if Bento4 version 1.5.0-617 is installed AND the system processes MP4/media files, particularly from untrusted or external sources.

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

Users should upgrade to a patched version of Bento4 or apply vendor-supplied patches. Until then, implement input validation to reject malformed MP4/media files before processing them with the vulnerable library.

Fix this in Bento4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2017-14645 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