Summary
imageproc: Out-of-bounds read via NaN coordinates in bilinear/bicubic sampling
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.
Impact
An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
imageproc to 0.23.1 or later; imageproc to 0.24.1 or later; imageproc to 0.25.1 or later; imageproc to 0.26.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-QG8R-F7X3-25F7? GHSA-QG8R-F7X3-25F7 is a medium-severity integer overflow or wraparound vulnerability in imageproc (rust), affecting versions < 0.23.1. It is fixed in 0.23.1, 0.24.1, 0.25.1, 0.26.2. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
- Which versions of imageproc are affected by GHSA-QG8R-F7X3-25F7? imageproc (rust) versions < 0.23.1 is affected.
- Is there a fix for GHSA-QG8R-F7X3-25F7? Yes. GHSA-QG8R-F7X3-25F7 is fixed in 0.23.1, 0.24.1, 0.25.1, 0.26.2. Upgrade to this version or later.
- Is GHSA-QG8R-F7X3-25F7 exploitable, and should I be worried? Whether GHSA-QG8R-F7X3-25F7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-QG8R-F7X3-25F7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-QG8R-F7X3-25F7?
- Upgrade
imageprocto 0.23.1 or later - Upgrade
imageprocto 0.24.1 or later - Upgrade
imageprocto 0.25.1 or later - Upgrade
imageprocto 0.26.2 or later
- Upgrade