CVE-2018-13847
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 · uneditedAn issue has been found in Bento4 1.5.1-624. It is a SEGV in AP4_StcoAtom::AdjustChunkOffsets in Core/Ap4StcoAtom.cpp.
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 confidenceA segmentation fault (SEGV) vulnerability exists in Bento4 version 1.5.1-624 within the AP4_StcoAtom::AdjustChunkOffsets function in Core/Ap4StcoAtom.cpp. The STCO atom contains chunk offset tables for MP4 files, and improper handling during offset adjustment leads to memory access violations, causing a denial-of-service condition when processing specially crafted MP4 files.
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= 1.5.1-624CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Bento4 library versionLocate the Bento4 library binary or header file and check its version metadata. If using command-line tools like mp4extract, run 'mp4extract --version' or check the library file properties. If linked as a library, inspect the library filename or embedded version string.Affected if The installed version is exactly 1.5.1-624
-
Confirm MP4 file processing capabilityDetermine whether your application or tool using Bento4 is configured to parse or manipulate MP4 files. Check configuration files, command-line arguments, or runtime settings that enable MP4 input handling.Affected if The application processes MP4 files as input
-
Verify STCO atom handling is in useExamine whether the MP4 parsing code path includes the STCO atom (chunk offset table) processing. This typically occurs when reading or modifying MP4 file structure, especially when adjusting chunk offsets during file modification or analysis.Affected if The application reads or modifies the STCO atom in MP4 files being processed
-
Check for untrusted MP4 input sourcesReview whether the system accepts MP4 files from external or untrusted sources without prior validation. This includes web uploads, file parsing services, or media processing pipelines handling content from users or external systems.Affected if MP4 files from untrusted or external sources are processed
You are affected if your Bento4 installation is exactly version 1.5.1-624 AND your application processes MP4 files that could contain crafted STCO atom data from potentially untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict processing of MP4 files from untrusted sources with Bento4 library until a patched version is available; implement input validation on STCO atom data before passing to AdjustChunkOffsets to prevent out-of-bounds memory access.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13847 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13847 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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