Summary
imageproc: integer overflow in kernel size check leads to out-of-bounds read
A bounds verification of a slice storage of a 2-dimensional matrix's coefficients (a kernel) would compare the total size against the product of individual dimensions. This would erroneously cast after the multiplication and consequently fail to detect possible violations when overflow occurs.
Afterwards, the individual sizes were trusted to properly constrain coordinates within the matrix to indices valid for the underlying storage. With a crafted Kernel object, certain combinations of coordinates could then cause an out-of-bounds access in an unsafe function while fulfilling its documented preconditions. The kernel value could be passed to library functions that trusted the preconditions and then performed such reads.
Impact
A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.
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-W5P8-4JCX-2J6R? GHSA-W5P8-4JCX-2J6R is a medium-severity out-of-bounds read 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. A read operation accesses a memory location beyond the intended buffer boundary.
- Which versions of imageproc are affected by GHSA-W5P8-4JCX-2J6R? imageproc (rust) versions < 0.23.1 is affected.
- Is there a fix for GHSA-W5P8-4JCX-2J6R? Yes. GHSA-W5P8-4JCX-2J6R is fixed in 0.23.1, 0.24.1, 0.25.1, 0.26.2. Upgrade to this version or later.
- Is GHSA-W5P8-4JCX-2J6R exploitable, and should I be worried? Whether GHSA-W5P8-4JCX-2J6R 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-W5P8-4JCX-2J6R 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-W5P8-4JCX-2J6R?
- 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