Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

heifer-isobmff

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5crates.ioPublished

    Memory exhaustion when parsing a crafted iloc box

    GHSA-3243-948x-x627

    Affected
    • crates.io heifer-isobmff >= 0.0.0-0, < 0.3.27
    Fixed in
    0.3.27· Vendor fix available
    Issue
    `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.

    Recommended action: Upgrade to 0.3.27 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.devSource checked Evidence →