Application crash via misplaced SDL chroma plane
Published Jun 26, 2024 · Updated Aug 2, 2024
Heap buffer overflow in libde265 1.0.15 allows context-dependent attackers to crash dec265 by opening a crafted H.265 stream. The display444as420 path places the U-plane pointer after half of the luma allocation instead of one quarter, then writes subsampled chroma bytes beyond the SDL texture buffer. The affected dec265 sample player must use SDL output to open a 4:4:4 stream; integrated library users without that renderer do not reach this crash path.
Summary
What happened
Heap buffer overflow in libde265 1.0.15 allows context-dependent attackers to crash dec265 by opening a crafted H.265 stream. The display444as420 path places the U-plane pointer after half of the luma allocation instead of one quarter, then writes subsampled chroma bytes beyond the SDL texture buffer. The affected dec265 sample player must use SDL output to open a 4:4:4 stream; integrated library users without that renderer do not reach this crash path.
The record
- CVE
- CVE-2024-38949
- Published
- Jun 26, 2024
- Updated
- Aug 2, 2024
- Vendor
- Struktur AG
- Product
- libde265
- Classifications
- CWE-122, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=v1.0.15
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Issue #460 dec265 crash inputsproof 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