Service interruption via unreleased byte buffer
Published May 26, 2023 · Updated Jan 14, 2025
Memory leak in MP4BytesProperty in mp4v2 2.1.2 allows attackers to exhaust process memory by supplying a crafted MP4 file. The MP4BytesProperty constructor allocates a byte buffer at mp4property.cpp:533, and malformed descriptor processing leaves the allocation unreleased. An application linked to the library must process the file; repeated inputs can consume memory and interrupt only that process.
Summary
What happened
Memory leak in MP4BytesProperty in mp4v2 2.1.2 allows attackers to exhaust process memory by supplying a crafted MP4 file. The MP4BytesProperty constructor allocates a byte buffer at mp4property.cpp:533, and malformed descriptor processing leaves the allocation unreleased. An application linked to the library must process the file; repeated inputs can consume memory and interrupt only that process.
The record
- CVE
- CVE-2023-33720
- Published
- May 26, 2023
- Updated
- Jan 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Jan 14, 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.
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
- poc_BytesProperty.mp4.zipproof 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