Memory exhaustion via unreleased GIF allocations
Published Sep 20, 2022 · Updated May 27, 2025
Memory leak in SWFTools gif2swf commit 772e55a2 allows context-dependent attackers to exhaust memory via a crafted GIF file. The conversion path retains allocations made by rfx_calloc in lib/mem.c and rfx_alloc in swf_ShapeAddBitmapFillStyle instead of releasing them. Exploitation requires a user to run gif2swf on the crafted file; repeated retained allocations exhaust available memory and interrupt conversion.
Summary
What happened
Memory leak in SWFTools gif2swf commit 772e55a2 allows context-dependent attackers to exhaust memory via a crafted GIF file. The conversion path retains allocations made by rfx_calloc in lib/mem.c and rfx_alloc in swf_ShapeAddBitmapFillStyle instead of releasing them. Exploitation requires a user to run gif2swf on the crafted file; repeated retained allocations exhaust available memory and interrupt conversion.
The record
- CVE
- CVE-2022-35085
- Published
- Sep 20, 2022
- Updated
- May 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 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.
Weakness, pattern, technique
Public exploit references
- gif2swf crafted-GIF memory-leak 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