Decoder crash via crafted HEVC file
Published Sep 16, 2021 · Updated Aug 4, 2024
A segmentation fault in libde265 1.0.4 allows attackers to crash a target application by supplying a crafted HEVC file. During sample adaptive offset postprocessing, apply_sao_internal dereferences an invalid address while decoding malformed stream state. The target must decode the file, and the demonstrated consequence is process termination rather than code execution.
Summary
What happened
A segmentation fault in libde265 1.0.4 allows attackers to crash a target application by supplying a crafted HEVC file. During sample adaptive offset postprocessing, apply_sao_internal dereferences an invalid address while decoding malformed stream state. The target must decode the file, and the demonstrated consequence is process termination rather than code execution.
The record
- CVE
- CVE-2020-21605
- Published
- Sep 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2021CVE 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
- Upstream apply_sao_internal crash fileproof 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