Advisory

RUSTSEC-2026-0458

Also known as: GHSA-3243-948x-x627

Summary

Memory exhaustion when parsing a crafted iloc box

Details

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`):
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.

Severity

Medium Basis: CVSS v3 score 6.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Dates

Published
2026-11-04 12:00 UTC
Modified
2026-11-09 10:00 UTC

Affected packages and fixes

heifer-isobmff

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.3.27 (semver)

Fixed versions

0.3.27

Fix

  • Fixed version 0.3.27
    cargo update -p heifer-isobmff --precise 0.3.27

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences