Memory leak via unreleased parsed strings
Published May 31, 2023 · Updated Jan 10, 2025
Memory leakage in MP4File::ReadString() in mp4v2 2.1.3 allows context-dependent attackers to consume memory via a crafted MP4 file. The function reallocates a buffer while parsing a null-terminated string, and MP4StringProperty::Read leaves the returned allocation unreleased. The condition requires a consumer that parses attacker-supplied media in a long-running process, where repeated parsing increases retained memory.
Summary
What happened
Memory leakage in MP4File::ReadString() in mp4v2 2.1.3 allows context-dependent attackers to consume memory via a crafted MP4 file. The function reallocates a buffer while parsing a null-terminated string, and MP4StringProperty::Read leaves the returned allocation unreleased. The condition requires a consumer that parses attacker-supplied media in a long-running process, where repeated parsing increases retained memory.
The record
- CVE
- CVE-2023-33718
- Published
- May 31, 2023
- Updated
- Jan 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted MP4 LeakSanitizer proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo