GHSA-qg8r-f7x3-25f7
imageproc: Out-of-bounds read via NaN coordinates in bilinear/bicubic sampling
Blast Radius
imageproc🦀imageproc🦀imageproc🦀imageprocReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | imageproc | all versions | 0.23.1 |
| 🦀crates.io | imageproc | ≥ 0.24.0&&< 0.24.1 | 0.24.1 |
| 🦀crates.io | imageproc | ≥ 0.25.0&&< 0.25.1 | 0.25.1 |
| 🦀crates.io | imageproc | ≥ 0.26.0&&< 0.26.2 | 0.26.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for imageproc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update imageproc to 0.23.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg8r-f7x3-25f7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qg8r-f7x3-25f7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qg8r-f7x3-25f7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qg8r-f7x3-25f7 in your dependencies?
O3 detects GHSA-qg8r-f7x3-25f7 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.