Process crash via invalid image-pointer free
Published May 6, 2021 · Updated Aug 3, 2024
Invalid pointer release in AOMedia libaom before 2021-04-07 allows remote attackers to crash a process through failed image allocation. In aom_image.c, img_alloc_helper routes allocation failures through aom_img_free, which can pass a non-heap image pointer to free(). Reachability requires a consuming application to invoke the image-allocation API with attacker-influenced parameters that trigger its failure path.
Summary
What happened
Invalid pointer release in AOMedia libaom before 2021-04-07 allows remote attackers to crash a process through failed image allocation. In aom_image.c, img_alloc_helper routes allocation failures through aom_img_free, which can pass a non-heap image pointer to free(). Reachability requires a consuming application to invoke the image-allocation API with attacker-influenced parameters that trigger its failure path.
The record
- CVE
- CVE-2021-30473
- Published
- May 6, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-763, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
No public exploit references are available in this record.
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