Process interruption via unreleased glyph buffers
Published Feb 28, 2024 · Updated Aug 13, 2024
Memory leak in LibMing 0.4.8 allows remote attackers to exhaust memory through a crafted SWF file processed by the parser. The parseSWF_GLYPHENTRY function allocates GlyphIndex and GlyphAdvance buffers for glyph entries but does not release them after parsing. A user must process the file with a LibMing parser utility; repeated allocations can exhaust memory and interrupt that process.
Summary
What happened
Memory leak in LibMing 0.4.8 allows remote attackers to exhaust memory through a crafted SWF file processed by the parser. The parseSWF_GLYPHENTRY function allocates GlyphIndex and GlyphAdvance buffers for glyph entries but does not release them after parsing. A user must process the file with a LibMing parser utility; repeated allocations can exhaust memory and interrupt that process.
The record
- CVE
- CVE-2024-24149
- Published
- Feb 28, 2024
- Updated
- Aug 13, 2024
- Vendor
- Ming Development Team
- Product
- LibMing
- Classifications
- CWE-401, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.4.8
What conditions does exploitation require?
What is affected?
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_GLYPHENTRY 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