GHSA-rmc9-8qp4-gjhx json
Panic on chroma QP offsets enabled with an empty offset list
published 10d ago modified 6d ago also RUSTSEC-2026-0460
- cvss
- 6.5
- version 3.1, OSV
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
An HEVC Range Extensions stream can set `cu_chroma_qp_offset_enabled_flag` in a slice while its picture parameter set carries an empty chroma QP offset list. The decoder then read the list at the signalled index, which panicked on the out-of-range access. A panic aborts the decoding thread, or the whole process when built with `panic = "abort"`. The crate forbids `unsafe` code, so there is no memory corruption.
Any application that decodes untrusted HEIC files or HEVC streams with `heifer-hevc-dec`, directly or through the `heifer` crate, is affected.
The flaw was corrected in 0.3.27 (commit [`1a8426e`](https://github.com/HarpeLm/Heifer/commit/1a8426e1b41160fb48d8baf8be858238570a8093)): with an empty list there is no offset to apply, and the offset is zero.
Patch / fix
Is GHSA-rmc9-8qp4-gjhx in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | heifer-hevc-dec | >=0.0.0-0, <0.3.27 |
0.3.27 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.