Process crash via unchecked decompiler buffer write
Published Dec 29, 2025 · Updated Dec 29, 2025
Heap-buffer overflow in libming 0.4.8 allows remote attackers to crash the swftophp utility with a crafted SWF file. During decompilation of deeply nested SWF actions, dcputchar writes output past the 40,960-byte heap buffer allocated by dcinit. Exploitation requires attacker-controlled SWF content to reach the decompiler; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Heap-buffer overflow in libming 0.4.8 allows remote attackers to crash the swftophp utility with a crafted SWF file. During decompilation of deeply nested SWF actions, dcputchar writes output past the 40,960-byte heap buffer allocated by dcinit. Exploitation requires attacker-controlled SWF content to reach the decompiler; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2025-66877
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 2025CVE publishedPublication date reported by the CVE source.
- Dec 29, 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.
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.
Weakness, pattern, technique
Public exploit references
- poc12 swftophp 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