CVE-2018-14532
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 was discovered in Bento4 1.5.1-624. There is a heap-based buffer over-read in AP4_Mpeg2TsVideoSampleStream::WriteSample in Core/Ap4Mpeg2Ts.cpp after a call from Mp42Hls.cpp, a related issue to CVE-2018-13846.
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 · high confidenceA heap-based buffer over-read vulnerability exists in Bento4 version 1.5.1-624 within the AP4_Mpeg2TsVideoSampleStream::WriteSample function in Core/Ap4Mpeg2Ts.cpp when processing HLS streams. The vulnerability occurs during MPEG-2 Transport Stream video sample writing, where insufficient bounds checking allows reading beyond allocated heap memory. This is a memory safety flaw exploitable during media file processing.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bento4 versionRun 'mp4info --version' or check the application binary metadata for Bento4 version stringAffected if Version is exactly 1.5.1-624 (only this specific build is vulnerable)
-
Confirm HLS stream processing is occurringReview application logs or network traffic to determine if MPEG-2 Transport Stream (MPEG-2 TS) HLS streams are being processedAffected if The application is actively processing HLS streams containing MPEG-2 TS video content
-
Inspect AP4_Mpeg2Ts.cpp build timestampIf source code or binary is accessible, check Core/Ap4Mpeg2Ts.cpp compilation date or verify the WriteSample function contains the vulnerable bounds check logicAffected if The source matches version 1.5.1-624 with unpatched WriteSample function
-
Monitor for crashes during media processingReview error logs or crash dumps for heap-buffer-over-read errors occurring during HLS/MPEG-2 TS video sample writing operationsAffected if Crashes occur specifically when writing MPEG-2 TS video samples from HLS streams
You are affected if you are running exactly Bento4 version 1.5.1-624 and actively processing HLS streams that contain MPEG-2 Transport Stream video content.
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 dataApply the vendor-supplied patch or upgrade to a Bento4 version beyond 1.5.1-624 that addresses this buffer over-read vulnerability in the MPEG-2 TS video sample stream handling.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14532 — 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-14532 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