Crash via out-of-bounds GIF extension block read
Published Sep 20, 2022 · Updated May 28, 2025
A heap buffer overflow in SWFTools gif2swf commit 772e55a2 allows local users to crash the converter with a crafted GIF file. The getGifDelayTime function reads one byte immediately past a libgif-allocated extension block while extracting the frame delay. Execution requires a user to process the malicious file, and the demonstrated consequence is an AddressSanitizer-detected abort.
Summary
What happened
A heap buffer overflow in SWFTools gif2swf commit 772e55a2 allows local users to crash the converter with a crafted GIF file. The getGifDelayTime function reads one byte immediately past a libgif-allocated extension block while extracting the frame delay. Execution requires a user to process the malicious file, and the demonstrated consequence is an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2022-35088
- Published
- Sep 20, 2022
- Updated
- May 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2022CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record 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
- SWFTools gif2swf crash sampleproof 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