Memory leak via unreleased export-asset allocations
Published Feb 20, 2025 · Updated Feb 21, 2025
Memory leak in libming 0.4.8 allows attackers to retain heap allocations via an SWF file containing export assets. The parseSWF_EXPORTASSETS function allocates tag and name arrays plus each name string but provides no corresponding deallocation path. The demonstrated input leaks 266 bytes per parse, so repeated processing grows memory use; the public record does not establish a crash or service interruption.
Summary
What happened
Memory leak in libming 0.4.8 allows attackers to retain heap allocations via an SWF file containing export assets. The parseSWF_EXPORTASSETS function allocates tag and name arrays plus each name string but provides no corresponding deallocation path. The demonstrated input leaks 266 bytes per parse, so repeated processing grows memory use; the public record does not establish a crash or service interruption.
The record
- CVE
- CVE-2025-26304
- Published
- Feb 20, 2025
- Updated
- Feb 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-244
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2025CVE publishedPublication date reported by the CVE source.
- Feb 21, 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
- Poc-parseSWF_EXPORTASSETS.zipproof 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