CVE-2023-33716
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 · uneditedmp4v2 v2.1.3 was discovered to contain a memory leak via the class MP4StringProperty at mp4property.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 confidencemp4v2 v2.1.3 contains a memory leak in the MP4StringProperty class within mp4property.cpp. Memory allocated for string properties is not properly freed during object destruction or cleanup, leading to gradual memory exhaustion when processing multiple 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= 2.1.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed mp4v2 versionRun 'dpkg -l | grep mp4v2' (Debian) or 'rpm -qa | grep mp4v2' (RHEL), or check the library file: 'strings /usr/lib/libmp4v2.so* | grep -i version'Affected if The version displayed is exactly 2.1.3
-
Inspect mp4property.cpp source codeLocate the mp4property.cpp file in your mp4v2 source or include directory. Search for the MP4StringProperty class destructor. Look for 'delete' or 'free' statements that should free the string buffer allocated for m_valueAffected if The destructor exists but contains no deallocation statements for the string member variable, or the fix commit (if available) is not applied
-
Check for memory leak indicators in mp4v2 libraryIf you have a binary linked against mp4v2, run 'ldd <binary> | grep mp4v2' to confirm linkage, then monitor memory usage while processing multiple MP4 files with the applicationAffected if Memory usage grows proportionally with the number of MP4 files processed and never stabilizes, indicating the leak is being triggered
-
Verify MP4StringProperty cleanup routineSearch the mp4property.cpp file for the MP4StringProperty::Dump or MP4StringProperty::Copy methods to see if they properly handle memory cleanupAffected if These methods copy or duplicate strings but do not free previously allocated memory, leaving the original allocation leaked
You are affected if mp4v2 version 2.1.3 is installed and you process MP4 files that utilize string properties, as the memory leak occurs during object cleanup for each file processed.
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 dataUpgrade to a patched version of mp4v2 if available, or implement proper memory deallocation in the MP4StringProperty class destructor and cleanup routines to ensure all allocated string memory is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33716 — 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-2023-33716 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