Crash via stale buffer pointer after realloc
Published Jan 19, 2024 · Updated Sep 11, 2024
Use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc via crafted ActionScript source. In bufferWriteData, bufferCheckSize reallocates the output buffer, but execution then reads through the stale pre-reallocation data pointer. Exploitation requires a user or local workflow to pass the crafted file to swfc; the published proof demonstrates a sanitizer-detected abort, while code execution remains unestablished.
Summary
What happened
Use-after-free in SWFTools 0.9.2 allows context-dependent attackers to crash swfc via crafted ActionScript source. In bufferWriteData, bufferCheckSize reallocates the output buffer, but execution then reads through the stale pre-reallocation data pointer. Exploitation requires a user or local workflow to pass the crafted file to swfc; the published proof demonstrates a sanitizer-detected abort, while code execution remains unestablished.
The record
- CVE
- CVE-2024-22920
- Published
- Jan 19, 2024
- Updated
- Sep 11, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 11, 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 bufferWriteData 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