Application crash via rate histogram stack overflow
Published Dec 2, 2021 · Updated Aug 4, 2024
Stack buffer overflow in AOM 2.0.1 rate histogram code allows attackers to crash an encoding process through crafted input. The flaw resides in stats/rate_hist.c, but public records do not identify the affected buffer, its bounds, or the write that exceeds them. Triggering requires user interaction with attacker-supplied data; SUSE bounds the consequence to application availability.
Summary
What happened
Stack buffer overflow in AOM 2.0.1 rate histogram code allows attackers to crash an encoding process through crafted input. The flaw resides in stats/rate_hist.c, but public records do not identify the affected buffer, its bounds, or the write that exceeds them. Triggering requires user interaction with attacker-supplied data; SUSE bounds the consequence to application availability.
The record
- CVE
- CVE-2020-36131
- 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.
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
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