Decoder crash via out-of-bounds chroma read
Published Sep 16, 2021 · Updated Aug 4, 2024
Heap buffer overflow in libde265 1.0.4 allows attackers to crash an H.265 decoder by supplying a crafted video file. The mc_chroma function reads two bytes immediately beyond an allocated image buffer while generating inter-prediction samples. Processing the file is required, and the demonstrated consequence is decoder termination rather than data disclosure or modification.
Summary
What happened
Heap buffer overflow in libde265 1.0.4 allows attackers to crash an H.265 decoder by supplying a crafted video file. The mc_chroma function reads two bytes immediately beyond an allocated image buffer while generating inter-prediction samples. Processing the file is required, and the demonstrated consequence is decoder termination rather than data disclosure or modification.
The record
- CVE
- CVE-2020-21597
- Published
- Sep 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 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
- libde265 mc_chroma heap-overflow proof-of-concept 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