Application crash via unchecked null packet
Published Apr 19, 2021 · Updated Aug 3, 2024
Null pointer dereference in GPAC 1.0.1 allows context-dependent attackers to crash the application with a crafted MP4 file. In latm_dmx_process, a control path leaves pck null when input has ended but buffered LATM data remains, then passes pck to gf_filter_pck_get_data. Processing the attacker-supplied file is required, and the dereference terminates the affected GPAC process without reported data disclosure or modification.
Summary
What happened
Null pointer dereference in GPAC 1.0.1 allows context-dependent attackers to crash the application with a crafted MP4 file. In latm_dmx_process, a control path leaves pck null when input has ended but buffered LATM data remains, then passes pck to gf_filter_pck_get_data. Processing the attacker-supplied file is required, and the dereference terminates the affected GPAC process without reported data disclosure or modification.
The record
- CVE
- CVE-2021-30199
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 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.
Public exploit references
- GPAC issue 1728 crafted MP4 fileproof 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