Application crash via decoder cleanup double free
Published Jun 25, 2021 · Updated Aug 4, 2024
Double free in miniaudio 0.10.35 allows context-dependent attackers to crash applications by supplying a crafted audio file. During decoder initialization, ma_default_vfs_close__stdio passes an already-closed stdio file handle to fclose, causing the allocator to free the same region again. Exposure requires a consuming application to open attacker-controlled audio through the affected file-decoder path; the demonstrated result is process abort.
Summary
What happened
Double free in miniaudio 0.10.35 allows context-dependent attackers to crash applications by supplying a crafted audio file. During decoder initialization, ma_default_vfs_close__stdio passes an already-closed stdio file handle to fclose, causing the allocator to free the same region again. Exposure requires a consuming application to open attacker-controlled audio through the affected file-decoder path; the demonstrated result is process abort.
The record
- CVE
- CVE-2021-34184
- Published
- Jun 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 25, 2021CVE 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.
Public exploit references
- POC1 malformed audio fileproof 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