Application crash via AVX2 out-of-bounds read
Published Dec 2, 2021 · Updated Aug 4, 2024
Out-of-bounds read in AOM 2.0.1 allows remote attackers to crash an application during AV1 media processing after user interaction. The AVX2 OBMC SAD implementation reads outside the intended buffer and faults in aom_dsp/x86/obmc_sad_avx2.c. Reaching the faulty x86 AVX2 path requires user interaction; the documented consequence is a crash without confidentiality or integrity impact.
Summary
What happened
Out-of-bounds read in AOM 2.0.1 allows remote attackers to crash an application during AV1 media processing after user interaction. The AVX2 OBMC SAD implementation reads outside the intended buffer and faults in aom_dsp/x86/obmc_sad_avx2.c. Reaching the faulty x86 AVX2 path requires user interaction; the documented consequence is a crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2020-36134
- Published
- Dec 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1203
- Attack vector
- network
- 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.
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