Skip to content

← Public intelligence

crates.io package

jxl-oxide

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.2crates.ioPublished

    jxl-oxide: FrameBuffer::new creates out-of-bounds slices on overflow

    GHSA-66m8-c62j-h6v5

    Affected
    • crates.io jxl-oxide <= 0.12.5
    Fixed in
    0.12.6· Vendor fix available
    Issue
    jxl-oxide exposes a public safe API that can construct an undersized FrameBuffer due to unchecked usize multiplication, which immediately trigger panic while initializing the buffer in normal decoding path. Additionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within jxl-oxide. Impact On 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.

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

    Sources:github.comSource checked Evidence →