Application crash via SSE chroma buffer over-read
Published Nov 2, 2022 · Updated May 2, 2025
Heap-buffer overflow in libde265 1.0.8 allows remote attackers to crash a decoding application by supplying a crafted H.265 video file. The ff_hevc_put_hevc_epel_pixels_8_sse routine in sse-motion.cc reads eight bytes beyond an allocated image buffer during chroma inter-prediction. Exploitation requires the file to be decoded with SSE acceleration and user interaction; the demonstrated consequence is process termination.
Summary
What happened
Heap-buffer overflow in libde265 1.0.8 allows remote attackers to crash a decoding application by supplying a crafted H.265 video file. The ff_hevc_put_hevc_epel_pixels_8_sse routine in sse-motion.cc reads eight bytes beyond an allocated image buffer during chroma inter-prediction. Exploitation requires the file to be decoded with SSE acceleration and user interaction; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2022-43235
- 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.
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.
Public exploit references
- FDU-Sec libde265 poc3proof 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