Process-memory consumption via repeated encoding allocation
Published Sep 13, 2021 · Updated Aug 3, 2024
A memory leak in MP4Box's infe_box_read in GPAC 1.0.1 allows attackers to consume process memory through a crafted media file. When an infe box contains more than two strings, the function replaces content_encoding with a new allocation without freeing the prior buffer. A user must make MP4Box process the crafted file; extra strings consume heap memory, while the cited records do not establish direct disclosure of prior contents.
Summary
What happened
A memory leak in MP4Box's infe_box_read in GPAC 1.0.1 allows attackers to consume process memory through a crafted media file. When an infe box contains more than two strings, the function replaces content_encoding with a new allocation without freeing the prior buffer. A user must make MP4Box process the crafted file; extra strings consume heap memory, while the cited records do not establish direct disclosure of prior contents.
The record
- CVE
- CVE-2021-33363
- Published
- Sep 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- 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