GHSA-5qv7-j6w5-fr4m — imageproc
GHSA-5qv7-j6w5-fr4m is a remote code execution vulnerability in imageproc. A fix is available for imageproc — see the affected versions and patch details below.
imageproc has fragile bounds check when sampling from image
Real-World Exposure
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 read of pixels was coded as modifying coordinates to lie within the image bounds. It would calculate a coordinate by adding a constant to an input and taking the minimum of the resulting coordinate and 'dimension - 1'. This would not protect against malicious inputs that could overflow the addition. Following the tricked bounds check, the image could then be sampled at multiple differently calculated coordinates that exceeded the bounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | imageproc | ≥ 0.24.0&&< 0.24.1 | 0.24.1cargo update -p imageproc --precise 0.24.1 |
| 🦀crates.io | imageproc | ≥ 0.25.0&&< 0.25.1 | 0.25.1cargo update -p imageproc --precise 0.25.1 |
| 🦀crates.io | imageproc | ≥ 0.26.0&&< 0.26.2 | 0.26.2cargo update -p imageproc --precise 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update imageproc to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5qv7-j6w5-fr4m 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5qv7-j6w5-fr4m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5qv7-j6w5-fr4m. 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-5qv7-j6w5-fr4m in your dependencies?
O3 Security finds GHSA-5qv7-j6w5-fr4m across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.