Denial of service via unreleased glyph allocations
Published Feb 28, 2024 · Updated Mar 27, 2025
Memory leak in parseSWF_TEXTRECORD in libming 0.4.8 allows context-dependent attackers to exhaust memory via a crafted SWF file. The function allocates a GlyphEntries array using the file-controlled glyph count but never frees that allocation after parsing. Processing the file with an affected libming consumer is required; repeated parsing can exhaust available memory and interrupt the consuming service.
Summary
What happened
Memory leak in parseSWF_TEXTRECORD in libming 0.4.8 allows context-dependent attackers to exhaust memory via a crafted SWF file. The function allocates a GlyphEntries array using the file-controlled glyph count but never frees that allocation after parsing. Processing the file with an affected libming consumer is required; repeated parsing can exhaust available memory and interrupt the consuming service.
The record
- CVE
- CVE-2024-24150
- Published
- Feb 28, 2024
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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
- parseSWF_TEXTRECORD crafted SWF 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