Process crash via expression parser over-read
Published Jan 19, 2024 · Updated Jun 5, 2025
Global buffer over-read in SWFTools 0.9.2 allows local users to crash swfc by processing a crafted SWFC script. parseExpression performs a four-byte read beyond global storage while a crafted edit-text value passes through parseTwip. Triggering the fault requires swfc to process the crafted input; the published proof of concept demonstrates an AddressSanitizer-detected process failure, not code execution.
Summary
What happened
Global buffer over-read in SWFTools 0.9.2 allows local users to crash swfc by processing a crafted SWFC script. parseExpression performs a four-byte read beyond global storage while a crafted edit-text value passes through parseTwip. Triggering the fault requires swfc to process the crafted input; the published proof of concept demonstrates an AddressSanitizer-detected process failure, not code execution.
The record
- CVE
- CVE-2024-22919
- Published
- Jan 19, 2024
- Updated
- Jun 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Jun 5, 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
- SWFTools issue 209 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