Application crash via null slice-header dereference
Published Jan 10, 2022 · Updated Aug 4, 2024
Out-of-bounds read in libde265 1.0.8 allows attackers to crash a decoding application by supplying a malformed HEVC file. The derive_boundaryStrength routine dereferences a null slice-header pointer while resolving reference-picture lists for invalid image regions. The target application must decode attacker-controlled HEVC content; successful exploitation interrupts that application through a segmentation fault.
Summary
What happened
Out-of-bounds read in libde265 1.0.8 allows attackers to crash a decoding application by supplying a malformed HEVC file. The derive_boundaryStrength routine dereferences a null slice-header pointer while resolving reference-picture lists for invalid image regions. The target application must decode attacker-controlled HEVC content; successful exploitation interrupts that application through a segmentation fault.
The record
- CVE
- CVE-2021-36411
- Published
- Jan 10, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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.
Weakness, pattern, technique
Public exploit references
- poc.zip malformed HEVC test caseproof 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