Process crash via freed dictionary pointer
Published Jan 19, 2024 · Updated Sep 12, 2024
Heap use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc when a user processes a crafted input file. The input function in lib/lex.swf5.c reads a dictionary-backed pointer after dict_free_all frees it during action-code parsing. Execution of swfc on the crafted file is required, and the demonstrated outcome is an AddressSanitizer abort that interrupts that process.
Summary
What happened
Heap use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc when a user processes a crafted input file. The input function in lib/lex.swf5.c reads a dictionary-backed pointer after dict_free_all frees it during action-code parsing. Execution of swfc on the crafted file is required, and the demonstrated outcome is an AddressSanitizer abort that interrupts that process.
The record
- CVE
- CVE-2024-22914
- Published
- Jan 19, 2024
- Updated
- Sep 12, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 12, 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
- SWFTools swfc heap-use-after-free 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