Memory retention via unreleased operating-points allocation
Published Sep 13, 2021 · Updated Aug 3, 2024
Memory leak in MP4Box in GPAC 1.0.1 allows attackers to consume process memory by supplying a crafted media file for parsing. In gf_isom_oinf_read_entry, an oversized layer count returns GF_NON_COMPLIANT_BITSTREAM without freeing the allocated operating-points structure. The trigger requires GPAC to parse attacker-supplied media; the public patch shows retained allocation rather than disclosure of memory contents.
Summary
What happened
Memory leak in MP4Box in GPAC 1.0.1 allows attackers to consume process memory by supplying a crafted media file for parsing. In gf_isom_oinf_read_entry, an oversized layer count returns GF_NON_COMPLIANT_BITSTREAM without freeing the allocated operating-points structure. The trigger requires GPAC to parse attacker-supplied media; the public patch shows retained allocation rather than disclosure of memory contents.
The record
- CVE
- CVE-2021-33366
- Published
- Sep 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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
No public exploit references are available in this record.
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