Code execution via stale image-dimension allocation
Published Mar 3, 2023 · Updated Mar 7, 2025
Heap buffer overflow in libde265 1.0.9 allows attackers to crash the decoder or execute code through a crafted H.265 bitstream. When image dimensions change without changing the total coding-tree-block count, alloc_image retains ctb_info with stale dimensions, and set_SliceAddrRS writes a two-byte slice address past that heap allocation. A user or automated decoding workflow must open the crafted file; the demonstrated result is a decoder abort, while code execution is a published impact rather than a demonstrated exploit.
Summary
What happened
Heap buffer overflow in libde265 1.0.9 allows attackers to crash the decoder or execute code through a crafted H.265 bitstream. When image dimensions change without changing the total coding-tree-block count, alloc_image retains ctb_info with stale dimensions, and set_SliceAddrRS writes a two-byte slice address past that heap allocation. A user or automated decoding workflow must open the crafted file; the demonstrated result is a decoder abort, while code execution is a published impact rather than a demonstrated exploit.
The record
- CVE
- CVE-2022-47665
- Published
- Mar 3, 2023
- Updated
- Mar 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 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
- 653.bin libde265 proof of conceptproof 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