Skip to content
Fencer Intel
medium 6.2

GHSA-66m8-c62j-h6v5 json

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

published 4mo ago modified 4mo ago

cvss
6.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary `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.

Patch / fix

  • crates.io jxl-oxide 0.12.6

Is GHSA-66m8-c62j-h6v5 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 Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io jxl-oxide
<0.12.6
0.12.6

Classification

Weakness
  • CWE-131 Incorrect Calculation of Buffer Size
  • CWE-190 Integer Overflow or Wraparound

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.