Application crash via unchecked HEVC tile count
Published Apr 19, 2021 · Updated Aug 3, 2024
Out-of-bounds write in GPAC 1.0.1 allows context-dependent attackers to crash the application by supplying a crafted HEVC file. The gf_hevc_read_pps_bs_internal parser uses an untrusted num_tile_columns value as the loop bound when writing the fixed-size pps->column_width array. The application must process the crafted file; the demonstrated consequence is an availability-only crash, with no reported data disclosure or modification.
Summary
What happened
Out-of-bounds write in GPAC 1.0.1 allows context-dependent attackers to crash the application by supplying a crafted HEVC file. The gf_hevc_read_pps_bs_internal parser uses an untrusted num_tile_columns value as the loop bound when writing the fixed-size pps->column_width array. The application must process the crafted file; the demonstrated consequence is an availability-only crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-30020
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- 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
- bug5 crafted HEVC filefunctional · 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