Application crash via freed tag-list pointer
Published Jan 19, 2024 · Updated May 30, 2025
Heap use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc via a crafted SWFC input file. During end-command processing, removeFromTo reads an eight-byte field through a pointer to a heap allocation already freed by c_end. Exploitation requires a user to run swfc on attacker-supplied input; the public demonstration produces an AddressSanitizer-detected abort, while code execution is not demonstrated.
Summary
What happened
Heap use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc via a crafted SWFC input file. During end-command processing, removeFromTo reads an eight-byte field through a pointer to a heap allocation already freed by c_end. Exploitation requires a user to run swfc on attacker-supplied input; the public demonstration produces an AddressSanitizer-detected abort, while code execution is not demonstrated.
The record
- CVE
- CVE-2024-22956
- Published
- Jan 19, 2024
- Updated
- May 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 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 issue 208 proof of conceptproof 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