Decoder crash via unchecked reference-image bit depth
Published Nov 2, 2022 · Updated May 2, 2025
Heap-buffer overflow in libde265 1.0.8 allows remote attackers to crash a decoder by supplying a crafted HEVC video file. The put_epel_hv_fallback motion-compensation path reads two bytes beyond an allocated image buffer when the reference and current images use different bit depths. Triggering the fault requires the crafted file to be decoded, so exploitation depends on user interaction or automated processing of untrusted video and results in decoder termination.
Summary
What happened
Heap-buffer overflow in libde265 1.0.8 allows remote attackers to crash a decoder by supplying a crafted HEVC video file. The put_epel_hv_fallback motion-compensation path reads two bytes beyond an allocated image buffer when the reference and current images use different bit depths. Triggering the fault requires the crafted file to be decoded, so exploitation depends on user interaction or automated processing of untrusted video and results in decoder termination.
The record
- CVE
- CVE-2022-43249
- Published
- Nov 2, 2022
- Updated
- May 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- 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.
Weakness, pattern, technique
Public exploit references
- poc11-1 and poc11-2 crash samplesproof 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