Code execution via unreleased swfdump allocations
Published May 31, 2022 · Updated Aug 4, 2024
Memory-management failure in SWFTools swfdump through 20201222 allows local users to execute code by processing a crafted SWF file. During input processing, allocations made through rfx_alloc and rfx_calloc remain unreleased, producing a 63,389-byte AddressSanitizer leak. Exploitation requires user interaction to run swfdump on attacker-controlled input; the public artifact demonstrates the leak, but the record does not disclose how it enables code execution.
Summary
What happened
Memory-management failure in SWFTools swfdump through 20201222 allows local users to execute code by processing a crafted SWF file. During input processing, allocations made through rfx_alloc and rfx_calloc remain unreleased, producing a 63,389-byte AddressSanitizer leak. Exploitation requires user interaction to run swfdump on attacker-controlled input; the public artifact demonstrates the leak, but the record does not disclose how it enables code execution.
The record
- CVE
- CVE-2021-42197
- Published
- May 31, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Weakness, pattern, technique
Public exploit references
- memory_leaks_pocproof 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