ImageResizer.Plugins.FreeImage
Affected
- introduced
0, last affected4.2.8(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Vulnerable version of libwebp and can be exploited with a malicious source image
Impact
This vulnerability affects deployments of FreeImage 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 remove FreeImage from your project, as it is not maintained and presents a massive security risk.
If you are using FreeImage via ImageResizer.Plugins.FreeImage, please utilize Imageflow or Imageflow.Server instead, or upgrade to ImageResizer 5 and use ImageResizer.Plugins.Imageflow (enable Prereleases on NuGet to access).
FreeImage 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](https://github.com/webmproject/libwebp/commit/2af26267cdfcb63a88e5c74a85927a12d6ca1d76 ) and released 1.3.2. FreeImage hasn't been updated since then and is presumed vulnerable.
Patches
None. FreeImage has not been updated in several years.
Workarounds
If you are using ImageResizer.Plugins.FreeImage, please utilize Imageflow or Imageflow.Server instead, or upgrade to ImageResizer 5 and use ImageResizer.Plugins.Imageflow (enable Prereleases on NuGet to access).
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
High Basis: The source's own band: HIGH
0, last affected 4.2.8 (ecosystem)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0