Service interruption via leaked morph-line allocations
Published Mar 27, 2025 · Updated Mar 28, 2025
Memory leak in libming 0.4.8 allows attackers to interrupt an application by supplying a crafted SWF file for parsing. The parseSWF_MORPHLINESTYLES function allocates 74,880 bytes while decoding a DefineMorphShape2 record but fails to release that allocation after parsing. Exploitation requires an application or user to process the file; repeated parsing consumes memory and can halt the affected process.
Summary
What happened
Memory leak in libming 0.4.8 allows attackers to interrupt an application by supplying a crafted SWF file for parsing. The parseSWF_MORPHLINESTYLES function allocates 74,880 bytes while decoding a DefineMorphShape2 record but fails to release that allocation after parsing. Exploitation requires an application or user to process the file; repeated parsing consumes memory and can halt the affected process.
The record
- CVE
- CVE-2025-29489
- Published
- Mar 27, 2025
- Updated
- Mar 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- Mar 28, 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
- libming-fuzz7 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