Local denial of service via heap overflow
Published Sep 21, 2021 · Updated Aug 4, 2024
Out-of-bounds write in GPAC 0.8.0 allows attackers to cause denial of service by supplying a crafted media file. The gf_hinter_track_process function in isom_hinter_track_process.c performs a heap write beyond the allocated buffer while processing crafted media data. The file must be opened or processed locally, and exploitation interrupts service without evidence of data modification.
Summary
What happened
Out-of-bounds write in GPAC 0.8.0 allows attackers to cause denial of service by supplying a crafted media file. The gf_hinter_track_process function in isom_hinter_track_process.c performs a heap write beyond the allocated buffer while processing crafted media data. The file must be opened or processed locally, and exploitation interrupts service without evidence of data modification.
The record
- CVE
- CVE-2020-23267
- Published
- Sep 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 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.
Public exploit references
No public exploit references are available in this record.
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