Crash via unchecked AV1 output PID
Published Apr 19, 2021 · Updated Aug 3, 2024
Null pointer dereference in GPAC 1.0.1 allows context-dependent attackers to crash the application via a crafted AV1 file. The av1dmx_parse_flush_sample function passes a null ctx.opid to packet allocation without validating that the output PID exists, and gf_filter_pck_new_alloc_internal dereferences it. Exploitation requires an application user to process the crafted file; the demonstrated consequence is a process crash 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 via a crafted AV1 file. The av1dmx_parse_flush_sample function passes a null ctx.opid to packet allocation without validating that the output PID exists, and gf_filter_pck_new_alloc_internal dereferences it. Exploitation requires an application user to process the crafted file; the demonstrated consequence is a process crash without reported data disclosure or modification.
The record
- CVE
- CVE-2021-30015
- 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
- bug2.zip crash reproducerproof 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