Local crash via undersized Base64 output buffer
Published Aug 16, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in SWFMill commit 53d7690 allows local users to crash the converter by opening a crafted SWF file. SWF::UnknownTag::writeXML allocates a three-byte destination for the triggering tag, and base64_encode writes a fourth byte past that heap allocation. Exploitation requires a local user to run swf2xml on attacker-supplied content; the public reproducer establishes process abortion, not code execution.
Summary
What happened
Heap-buffer overflow in SWFMill commit 53d7690 allows local users to crash the converter by opening a crafted SWF file. SWF::UnknownTag::writeXML allocates a three-byte destination for the triggering tag, and base64_encode writes a fourth byte past that heap allocation. Exploitation requires a local user to run swf2xml on attacker-supplied content; the public reproducer establishes process abortion, not code execution.
The record
- CVE
- CVE-2022-36144
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- SWFMill base64_encode crash reproducerproof 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