Decoder crash via coding-unit table over-read
Published Dec 7, 2023 · Updated Aug 28, 2024
Global buffer overflow in Struktur AG libde265 1.0.14 allows context-dependent attackers to crash decoders with a crafted H.265 bitstream. During coding-unit parsing, read_coding_unit reads one byte at an address 14 bytes beyond the 16-byte ctxIdxMap table. A user must decode the supplied stream; the public reproducer demonstrates an AddressSanitizer-detected abort, while code execution is not established.
Summary
What happened
Global buffer overflow in Struktur AG libde265 1.0.14 allows context-dependent attackers to crash decoders with a crafted H.265 bitstream. During coding-unit parsing, read_coding_unit reads one byte at an address 14 bytes beyond the 16-byte ctxIdxMap table. A user must decode the supplied stream; the public reproducer demonstrates an AddressSanitizer-detected abort, while code execution is not established.
The record
- CVE
- CVE-2023-49468
- Published
- Dec 7, 2023
- Updated
- Aug 28, 2024
- Vendor
- Struktur AG
- Product
- libde265
- Classifications
- CWE-787, CWE-120, T1203
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 7, 2023CVE publishedPublication date reported by the CVE source.
- Aug 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.14
What conditions does exploitation require?
What is affected?
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
- Proof-of-concept H.265 bitstreamproof 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