Skip to content
OpenAdvisories
Medium · 6.5 GHSA-3243-948x-x627 RUSTSEC-2026-0458

Memory exhaustion when parsing a crafted `iloc` box

Published Nov 4, 2026 · Updated Nov 9, 2026 · Assigned by RUSTSEC

Description

`heifer-isobmff` read the item and extent counts of the `iloc` box (item
locations) from the file and allocated memory for them before checking that the
box was large enough to hold that many entries. Extents that declare no field at
all take zero bytes each, so a small crafted file could declare an enormous
number of them. A 42 KB file made parsing allocate several gigabytes, which can
exhaust memory and abort the process.

Any application that parses untrusted HEIF/HEIC files with `heifer-isobmff`,
directly or through the `heifer` crate, is affected: `HeifFile::parse` and every
decoding and metadata function built on it.

The flaw was corrected in 0.3.27 (commit
[`1a8426e`](https://github.com/HarpeLm/Heifer/commit/1a8426e1b41160fb48d8baf8be858238570a8093)):
item and extent counts are bounded by the size of the box, extents that carry no
field are rejected, and the total number of extents is capped.

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io heifer-isobmff >= 0.0.0-0, < 0.3.27 0.3.27 RUSTSEC-2026-0458

References