GHSA-7vpr-3ppw-qrpj
HIGHImageflow affected by libwebp zero-day and should not be used with malicious source images.
Blast Radius
Imageflow.AllPlatforms.NETImageflow.NativeRuntime.win-x86_64.NETImageflow.NativeRuntime.osx-x86_64.NETImageflow.NativeRuntime.win-x86.NETImageflow.NativeRuntime.ubuntu-x86_64.NETImageflow.NativeRuntime.ubuntu-x86_64-haswell.NETImageflow.NativeTool.win-x86_64.NETImageflow.NativeTool.osx-x86_64+13 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This vulnerability affects deployments of Imageflow that involve decoding or processing malicious source .webp files. If you only process your own trusted files, this should not affect you (but you should update anyway).
Imageflow relies on Google's [libwebp] library to decode .webp images, and is affected by the recent zero-day out-of-bounds write vulnerability CVE-2023-4863 and https://github.com/advisories/GHSA-j7hp-h8jx-5ppr. The libwebp vulnerability also affects Chrome, Android, macOS, and other consumers of the library).
libwebp patched the vulnerability and released 1.3.2
This was patched in libwebp-sys in 0.9.3 and 0.9.4
Imageflow v2.0.0-preview8 uses the patched version of libwebp as well as updated versions of all dependencies.
Note: preview 8 requires libc 2.31 or higher on linux and macOS 11 or higher. These restrictions are due to the oldest supported versions of those platforms (which is reflected on Github Actions).
Patches
Imageflow v2.0.0-preview8 use the patched version (v1.3.2) of libwebp and libwebp-sys 0.9.4. Imageflow.AllPlatforms 0.10.2 is patched Imageflow.Server v0.8.2 is patched ImageResizer.Plugins.Imageflow 5.0.12 is patched
Workarounds
Disable webp decoding using EnabledCodecs::disable_decoder(NamedDecoders::WebPDecoder) if using the Rust API.
Only files that meet the following criteria will be passed to libwebp:
bytes.starts_with(b"RIFF") && bytes[8..12].starts_with(b"WEBP")
You can utilize matching logic to block webp inputs in your language of choice.
References
https://github.com/advisories/GHSA-j7hp-h8jx-5ppr https://nvd.nist.gov/vuln/detail/CVE-2023-4863 https://github.com/webmproject/libwebp/commit/2af26267cdfcb63a88e5c74a85927a12d6ca1d76 https://github.com/NoXF/libwebp-sys/commits/master
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Imageflow.AllPlatforms | all versions | 0.10.2 |
| .NETNuGet | Imageflow.NativeRuntime.win-x86_64 | all versions | 2.0.0-preview6 |
| .NETNuGet | Imageflow.NativeRuntime.osx-x86_64 | all versions | 2.0.0-preview6 |
| .NETNuGet | Imageflow.NativeRuntime.win-x86 | all versions | 2.0.0-preview6 |
| .NETNuGet | Imageflow.NativeRuntime.ubuntu-x86_64 | all versions | 2.0.0-preview6 |
| .NETNuGet | Imageflow.NativeRuntime.ubuntu-x86_64-haswell | all versions | 2.0.0-preview6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Imageflow.AllPlatforms. 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 Imageflow.AllPlatforms to 0.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7vpr-3ppw-qrpj 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-7vpr-3ppw-qrpj 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-7vpr-3ppw-qrpj. 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-7vpr-3ppw-qrpj in your dependencies?
O3 detects GHSA-7vpr-3ppw-qrpj across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.