Application crash via unchecked SWF allocation
Published Jan 6, 2022 · Updated Aug 4, 2024
Memory exhaustion in libming 0.4.8 allows remote attackers to crash SWF-processing applications through a crafted compressed SWF file. The cws2fws function in util/main.c trusts the attacker-controlled uncompressed-size field and passes it directly to realloc without a bounds check. A user or application must process the file; the resulting oversized allocation failure terminates the affected process without reported data exposure or modification.
Summary
What happened
Memory exhaustion in libming 0.4.8 allows remote attackers to crash SWF-processing applications through a crafted compressed SWF file. The cws2fws function in util/main.c trusts the attacker-controlled uncompressed-size field and passes it directly to realloc without a bounds check. A user or application must process the file; the resulting oversized allocation failure terminates the affected process without reported data exposure or modification.
The record
- CVE
- CVE-2021-44590
- Published
- Jan 6, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- Proof-of-concept SWF for cws2fws allocation failureproof 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