Memory exhaustion via leaked XMT descriptors
Published Nov 2, 2022 · Updated May 2, 2025
Memory leak in GPAC 2.1-DEV-rev368-gfd054169b-master allows local users to exhaust process memory via a crafted XMT file. When malformed XML aborts scene loading, gf_odf_new_iod and nested descriptor constructors leave their allocated objects unreleased. The user must direct MP4Box to process the file; repeated parsing consumes memory and interrupts availability without reported data disclosure or modification.
Summary
What happened
Memory leak in GPAC 2.1-DEV-rev368-gfd054169b-master allows local users to exhaust process memory via a crafted XMT file. When malformed XML aborts scene loading, gf_odf_new_iod and nested descriptor constructors leave their allocated objects unreleased. The user must direct MP4Box to process the file; repeated parsing consumes memory and interrupts availability without reported data disclosure or modification.
The record
- CVE
- CVE-2022-43255
- Published
- Nov 2, 2022
- Updated
- May 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2022CVE publishedPublication date reported by the CVE source.
- May 2, 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
- poc1.xmt GPAC memory-leak 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