imgproxy heap overflow in ICO loader integer handling
imgproxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/imgproxy/imgproxy/v3 Go |
|
|
| github.com/imgproxy/imgproxy/v2 Go |
|
|
imgproxy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/imgproxy/imgproxy/v3 Go |
|
|
| github.com/imgproxy/imgproxy/v2 Go |
|
|
| github.com/imgproxy/imgproxy Go |
|
|
| github.com/imgproxy/imgproxy/v4 Go |
|
|
imgproxy from 4.0.0 before 4.0.16 contains an integer overflow in the ICO loader that allows remote attackers to trigger a heap buffer overflow via a crafted data_size value. Attackers can submit a crafted ICO image whose data_size wraps the allocation in vips/icoload.c, corrupting heap memory to crash the process or achieve code execution.
From the CVE record · VulnCheck
imgproxy 4.0.0 through versions before 4.0.16 has an integer overflow in its ICO loader. A remote attacker can submit a crafted ICO image to corrupt heap memory, potentially crashing the process or executing code. The input does not specify authentication or user-interaction requirements.
Engineers running imgproxy 4.0.0 through versions before 4.0.16, including the listed Go packages, should check their deployments.