dbcve.org
Bento4Application · Axiosys

CVE-2018-13846

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue has been found in Bento4 1.5.1-624. AP4_Mpeg2TsVideoSampleStream::WriteSample in Core/Ap4Mpeg2Ts.cpp has a heap-based buffer over-read after a call from Mp42Ts.cpp, a related issue to CVE-2018-14532.

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

Heap-based buffer over-read vulnerability in Bento4's AP4_Mpeg2TsVideoSampleStream::WriteSample function (Core/Ap4Mpeg2Ts.cpp) when processing MPEG-2 Transport Stream video samples. The issue occurs during sample writing operations triggered from Mp42Ts.cpp, indicating insufficient bounds checking when handling potentially malformed TS streams.

MitigationUpdate to a patched version of Bento4 if available; otherwise, implement proper bounds validation in the WriteSample function to ensure read operations stay within buffer boundaries before accessing memory.

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.1-624

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Verify Bento4 installation
    Search for Bento4 binaries or libraries on the system. Common file names include Mp42Ts, Mp4Encrypt, Mp4Decrypt, Ap4Mpeg2Ts, and libAP4.so/dll. Use commands like 'find / -name "*bento*"' or 'where *bento*' on Windows.
    Affected if Bento4 executables or libraries are present on the system
  2. Determine Bento4 version
    Run the Bento4 command-line tool with a version flag. For Mp42Ts, try 'Mp42Ts --version' or './Mp42Ts' without arguments. Check the binary metadata or any bundled version file.
    Affected if The installed version is 1.5.1-624
  3. Identify usage of MPEG-2 TS processing
    Review logs, scripts, or automation that invoke Mp42Ts to process .ts (Transport Stream) files. The vulnerable code path is triggered when writing MPEG-2 TS video samples.
    Affected if Mp42Ts or related tools are used to process MPEG-2 Transport Stream files
  4. Check for malformed TS input files
    Inspect any MPEG-2 TS files being processed. The vulnerability is triggered when handling malformed TS streams that cause WriteSample to read beyond buffer boundaries.
    Affected if The system processes untrusted or potentially malformed .ts files with Bento4

A system is affected if Bento4 version 1.5.1-624 is installed and is used to process MPEG-2 Transport Stream files, particularly potentially malformed ones.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Bento4 if available; otherwise, implement proper bounds validation in the WriteSample function to ensure read operations stay within buffer boundaries before accessing memory.

Recommended fix Moderate confidence

Latest stable release from Bento4 GitHub repository (version > 1.5.1-624)

  1. 1. Identify all applications or systems using Bento4 version 1.5.1-624
  2. 2. Download the latest stable release of Bento4 from the official GitHub repository (github.com/axiomatic-systems/Bento4)
  3. 3. Replace the vulnerable Bento4 library binaries or source code with the updated version
  4. 4. Rebuild and recompile any applications that link against the Bento4 library
  5. 5. Retest the functionality to ensure the update does not break existing features
  6. 6. Deploy the updated version to all affected production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bento4 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-2018-13846 — 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-2018-13846 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