Process memory exhaustion via unreleased parsing buffers
Published Jun 1, 2023 · Updated Jan 9, 2025
Memory leak in MP4SdpAtom::Read in mp4v2 2.1.3 allows context-dependent attackers to exhaust process memory via a crafted MP4 file. The CVE attributes the leak to MP4SdpAtom::Read, while its cited proof of concept shows unreleased buffers in MP4File string-reading paths. A user must cause an affected application to parse a crafted file; repeated processing can consume memory and interrupt the process.
Summary
What happened
Memory leak in MP4SdpAtom::Read in mp4v2 2.1.3 allows context-dependent attackers to exhaust process memory via a crafted MP4 file. The CVE attributes the leak to MP4SdpAtom::Read, while its cited proof of concept shows unreleased buffers in MP4File string-reading paths. A user must cause an affected application to parse a crafted file; repeated processing can consume memory and interrupt the process.
The record
- CVE
- CVE-2023-33719
- Published
- Jun 1, 2023
- Updated
- Jan 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 9, 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
- poc.zip memory-leak test casesproof 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