Imageflow affected by libwebp zero-day and should not be used with malicious source images.

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 patchedImageflow.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