imgproxy denial of service in ICO loader BMP header reconstruction
imgproxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/imgproxy/imgproxy/v3 Go |
|
|
| github.com/imgproxy/imgproxy Go |
| No fix yet |
| github.com/imgproxy/imgproxy/v2 |
imgproxy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/imgproxy/imgproxy/v3 Go |
|
|
| github.com/imgproxy/imgproxy Go |
| No fix yet |
| github.com/imgproxy/imgproxy/v2 |
|
| No fix yet |
| github.com/imgproxy/imgproxy/v4 Go |
|
|
imgproxy 3.3.0 before 4.0.17 contains an out-of-bounds heap read and write in the ICO loader's BMP header reconstruction (vips_foreign_load_ico_header in vips/icoload.c) when an ICO entry declares a tiny data size, causing unvalidated header fields to be read and written past the allocated buffer. Unauthenticated remote attackers can supply a crafted ICO image to corrupt adjacent heap chunk metadata, triggering a glibc abort that crashes the worker.
From the CVE record · VulnCheck
The ICO loader in affected imgproxy versions reads and writes beyond an allocated buffer when an ICO entry declares a tiny data size. An unauthenticated remote attacker can supply a crafted ICO image that corrupts heap metadata and crashes the worker.
Operators running Go github.com/imgproxy/imgproxy/v3 versions 3.3.0 through versions before 4.0.17, github.com/imgproxy/imgproxy/v4 versions before 4.0.17, or any version of the unversioned or v2 packages should check.