Code execution via overflowing stco offset allocation
Published Aug 18, 2021 · Updated Aug 3, 2024
Integer overflow in GPAC 1.0.1 MPEG-4 decoding allows context-dependent attackers to corrupt memory via a crafted video. In stco_box_read, a 32-bit offset count is multiplied by sizeof(u32) without an overflow guard, allocating an undersized offsets array before the parser fills it. Exploitation requires a user to open the file on a 32-bit build; the out-of-bounds writes can crash the process or execute code in its context.
Summary
What happened
Integer overflow in GPAC 1.0.1 MPEG-4 decoding allows context-dependent attackers to corrupt memory via a crafted video. In stco_box_read, a 32-bit offset count is multiplied by sizeof(u32) without an overflow guard, allocating an undersized offsets array before the parser fills it. Exploitation requires a user to open the file on a 32-bit build; the out-of-bounds writes can crash the process or execute code in its context.
The record
- CVE
- CVE-2021-21844
- Published
- Aug 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-680, CWE-119, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=GPAC Project Advanced Content commit a8a8d412dabcb129e695c3e7d861fcc81f608304 ,GPAC Project Advanced Content v1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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