Skip to main content
VulnerabilityPublished Updated

Imageproc: Fragile bounds check when sampling from image

Affects imageprocSource GCVE Database

0

Fixed in 0.26.2 : update imageproc when convenient.

Data as of 27 Oct 2026, 00:07 UTC

Severity
Unrated

Rated by Threat Radar

Patch
Available – fixed in 0.26.2, 0.25.1, 0.24.1 +1

What to do

Upgrade imageproc to 0.26.2, 0.25.1, 0.24.1 or 0.23.1.

Affected software

ProductAffectedFixed in
crates.ioimageprocpkg:cargo/imageprocOther threatsAffected
  • >=0.0.0-0 <0.23.1
  • >=0.24.0 <0.24.1
  • >=0.25.0 <0.25.1
  • >=0.26.0 <0.26.2
Fixed in
  • 0.23.1
  • 0.24.1
  • 0.25.1
  • 0.26.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A bounds check was performed in floating points before a cast to the index passed to an unchecked access function. This checked considered `NaN` cases improperly, causing them to succeed the check instead of failing it. The floating point coordinate is under caller control by passing a selected projection matrix. Carefully controlling the coordinates of an image with no data and one non-zero dimension provides an arbitrary read primitive in the first 32-bits of address space with a Bilinear sampling method. Using bicubic sampling can result in a read of a few bytes beyond an allocation. Other out-of-bounds reads may be possible.

References

Community reviews

Loading reviews…