Converter crash via unchecked frame-delay index
Published Dec 28, 2021 · Updated Aug 4, 2024
Heap buffer overflow in gif2apng 1.9 allows context-dependent attackers to crash the converter through a crafted GIF file. The main function allocates two bytes per counted frame for delays, then writes delays[n] after a trailing graphics-control extension when n equals the frame count. Processing the file is required; the demonstrated write corrupts two heap bytes past the allocation and terminates the process.
Summary
What happened
Heap buffer overflow in gif2apng 1.9 allows context-dependent attackers to crash the converter through a crafted GIF file. The main function allocates two bytes per counted frame for delays, then writes delays[n] after a trailing graphics-control extension when n equals the frame count. Processing the file is required; the demonstrated write corrupts two heap bytes past the allocation and terminates the process.
The record
- CVE
- CVE-2021-45911
- Published
- Dec 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 28, 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
- Crafted GIF crash reproducerproof 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