Process crash via freed-list dereference in gf_list_count
Published Mar 24, 2020 · Updated Aug 5, 2024
Use-after-free in libgpac.a in GPAC before 0.8.0 allows local users to crash MP4Box by processing a crafted MP4 file. During MPEG-TS program-map processing, gf_m2ts_process_pmt passes a freed list pointer to gf_list_count, which dereferences it. A local user must cause MP4Box to inspect the file; the documented consequence is a process crash, with no demonstrated code execution.
Summary
What happened
Use-after-free in libgpac.a in GPAC before 0.8.0 allows local users to crash MP4Box by processing a crafted MP4 file. During MPEG-TS program-map processing, gf_m2ts_process_pmt passes a freed list pointer to gf_list_count, which dereferences it. A local user must cause MP4Box to inspect the file; the documented consequence is a process crash, with no demonstrated code execution.
The record
- CVE
- CVE-2019-20631
- Published
- Mar 24, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-763, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- PoC_segv_gf_list_countproof 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