Decoder crash via out-of-bounds chroma read
Published Nov 2, 2022 · Updated May 2, 2025
Stack buffer overflow in libde265 1.0.8 allows context-dependent attackers to crash a decoder with a crafted H.265 video file. The put_epel_hv_fallback routine reads two bytes beyond the stack-allocated mcbuffer while generating chroma inter-prediction samples from malformed stream data. A victim application must decode the file; the demonstrated consequence is decoder termination under AddressSanitizer, not code execution.
Summary
What happened
Stack buffer overflow in libde265 1.0.8 allows context-dependent attackers to crash a decoder with a crafted H.265 video file. The put_epel_hv_fallback routine reads two bytes beyond the stack-allocated mcbuffer while generating chroma inter-prediction samples from malformed stream data. A victim application must decode the file; the demonstrated consequence is decoder termination under AddressSanitizer, not code execution.
The record
- CVE
- CVE-2022-43237
- Published
- Nov 2, 2022
- Updated
- May 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2022CVE publishedPublication date reported by the CVE source.
- May 2, 2025Record 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
- poc10 crafted H.265 bitstreamsproof 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