Local crash via unchecked SAO band indexing
Published Apr 7, 2025 · Updated Apr 9, 2025
Stack buffer overflow in libde265 before 1.0.5 allows local users to crash HEIF/HEVC decoders with a crafted image. In apply_sao_internal, an excessive bit depth makes bandShift reach at least eight, but the vulnerable code indexes the 32-entry bandTable before checking that condition. Processing attacker-supplied HEIF or HEVC data through the libde265 decoding backend is required; the public proof of concept demonstrates a crash, not code execution.
Summary
What happened
Stack buffer overflow in libde265 before 1.0.5 allows local users to crash HEIF/HEVC decoders with a crafted image. In apply_sao_internal, an excessive bit depth makes bandShift reach at least eight, but the vulnerable code indexes the 32-entry bandTable before checking that condition. Processing attacker-supplied HEIF or HEVC data through the libde265 decoding backend is required; the public proof of concept demonstrates a crash, not code execution.
The record
- CVE
- CVE-2025-29482
- Published
- Apr 7, 2025
- Updated
- Apr 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2025CVE publishedPublication date reported by the CVE source.
- Apr 9, 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.
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
- libheif file_fuzzer 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