Application crash via stack buffer overflow
Published Dec 2, 2021 · Updated Aug 4, 2024
Stack buffer overflow in AOM 2.0.1 allows context-dependent attackers to crash an application via unspecified vectors. The flaw resides in src/aom_image.c, but public records do not identify the affected function, destination stack buffer, or unchecked operation. User interaction is required; SUSE bounds the consequence to an application crash, while NVD assigns broader potential impacts.
Summary
What happened
Stack buffer overflow in AOM 2.0.1 allows context-dependent attackers to crash an application via unspecified vectors. The flaw resides in src/aom_image.c, but public records do not identify the affected function, destination stack buffer, or unchecked operation. User interaction is required; SUSE bounds the consequence to an application crash, while NVD assigns broader potential impacts.
The record
- CVE
- CVE-2020-36129
- Published
- Dec 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 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.
Weakness, pattern, technique
Public exploit references
- aomenc incompatible-option crash reproducerproof 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