CVE-2018-14446
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 · uneditedMP4Integer32Property::Read in atom_avcC.cpp in MP4v2 2.1.0 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted MP4 file.
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 overflow vulnerability exists in MP4v2 version 2.1.0 within the MP4Integer32Property::Read function in atom_avcC.cpp. The vulnerability is triggered when parsing a specially crafted MP4 file containing a maliciously constructed atom_avcC (AVC configuration) atom, allowing remote attackers to potentially execute arbitrary code or cause denial of service.
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= 2.1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Locate MP4v2 library in the environmentSearch for libmp4v2.so (Linux), mp4v2.dll (Windows), or libmp4v2.dylib (macOS). Use commands like 'find / -name "*mp4v2*"' on Linux, or check common paths such as /usr/lib, /usr/local/lib, or the application's dependency folders.Affected if MP4v2 library is present on the system and being used by any application
-
Determine installed MP4v2 versionRun 'mp4v2-config --version' if available, or inspect the library file metadata. On Linux, use 'ldd <application> | grep mp4v2' to find which application links to it, then check the library version via 'strings libmp4v2.so | grep -i version' or the package manager.Affected if The version is exactly 2.1.0
-
Identify applications or services that parse MP4 filesReview running processes that handle media files. Check application logs, dependencies, or configuration to confirm MP4v2 is used for MP4 file parsing. Look for services that process video files from untrusted sources.Affected if Any application uses MP4v2 to parse MP4 files, particularly those that could receive files from untrusted sources
-
Inspect MP4 files for atom_avcC contentUse a tool like 'mp4dump' or 'ffprobe' to examine MP4 files. Look for the 'avcC' atom within the file structure. This atom contains AVC configuration data and is the attack vector for this vulnerability.Affected if The environment processes MP4 files containing the atom_avcC (AVC configuration) atom
You are affected if MP4v2 version 2.1.0 is installed and any application uses it to parse MP4 files from untrusted sources that contain the atom_avcC atom.
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 dataUpdate MP4v2 library to a version containing the security fix. If no patched version is available, implement strict input validation on MP4 files before processing and consider sandboxing or restricting processing of untrusted MP4 content.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14446 — 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-14446 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