Process interruption via unreleased fill-style array allocations
Published Feb 28, 2024 · Updated Aug 29, 2024
Memory leak in LibMing 0.4.8 allows context-dependent attackers to exhaust process memory by supplying a crafted SWF file. parseSWF_FILLSTYLEARRAY reads a file-controlled fill-style count, allocates that many SWF_FILLSTYLE entries, and never releases the resulting heap allocation. A user or application must process the file with an affected utility, causing memory consumption that can interrupt that process.
Summary
What happened
Memory leak in LibMing 0.4.8 allows context-dependent attackers to exhaust process memory by supplying a crafted SWF file. parseSWF_FILLSTYLEARRAY reads a file-controlled fill-style count, allocates that many SWF_FILLSTYLE entries, and never releases the resulting heap allocation. A user or application must process the file with an affected utility, causing memory consumption that can interrupt that process.
The record
- CVE
- CVE-2024-24147
- Published
- Feb 28, 2024
- Updated
- Aug 29, 2024
- Vendor
- Ming Development Team
- Product
- LibMing
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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_FILLSTYLEARRAY 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