Process crash via unterminated TextConfig buffer
Published Sep 7, 2021 · Updated Aug 4, 2024
Heap-based buffer over-read in GPAC 0.8.0 allows attackers to crash the process by parsing a crafted TextConfig box. The txtc_Read function fills a size-bounded heap buffer without guaranteeing a null terminator, then gf_strdup scans beyond that allocation for one. Reaching the flaw requires GPAC to parse attacker-controlled media containing the malformed box; the demonstrated consequence is a process crash.
Summary
What happened
Heap-based buffer over-read in GPAC 0.8.0 allows attackers to crash the process by parsing a crafted TextConfig box. The txtc_Read function fills a size-bounded heap buffer without guaranteeing a null terminator, then gf_strdup scans beyond that allocation for one. Reaching the flaw requires GPAC to parse attacker-controlled media containing the malformed box; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2020-19750
- Published
- Sep 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- TextConfig unterminated-string proof of conceptproof of concept · unverified
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