Process crash via null prediction buffer write
Published Mar 1, 2023 · Updated Mar 7, 2025
NULL pointer dereference in libde265 1.0.10 allows attackers to crash a decoding process by supplying a crafted HEVC input file. During inter prediction, put_unweighted_pred_16_fallback writes decoded output through a null destination pointer at fallback-motion.cc line 179. The crafted file must be processed by an application using the library, so the demonstrated consequence is a process crash and service interruption.
Summary
What happened
NULL pointer dereference in libde265 1.0.10 allows attackers to crash a decoding process by supplying a crafted HEVC input file. During inter prediction, put_unweighted_pred_16_fallback writes decoded output through a null destination pointer at fallback-motion.cc line 179. The crafted file must be processed by an application using the library, so the demonstrated consequence is a process crash and service interruption.
The record
- CVE
- CVE-2023-24757
- Published
- Mar 1, 2023
- Updated
- Mar 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 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
- Crafted HEVC crash 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