CVE-2025-24354: imgproxy is vulnerable to SSRF against 0.0.0.0
Summary Imgproxy does not block the 0.0.0.0 address, even with IMGPROXYALLOWLOOPBACKSOURCEADDRESSES set to false. This can expose services on the local host. Details imgproxy protects against SSRF against a loopback address with the following check (source): This check is insufficient to prevent accessing services on the local host, as services may receive traffic on 0.0.0.0.
Published Jan 27, 2025
Affected packages
github.com/imgproxy/imgproxy
- Ecosystem
- Go
- Affected
- < 3.27.2
- Fixed in
- 3.27.2
- Check
go list -m github.com/imgproxy/imgproxy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Imgproxy does not block the 0.0.0.0 address, even with IMGPROXY_ALLOW_LOOPBACK_SOURCE_ADDRESSES set to false. This can expose services on the local host.
Details
imgproxy protects against SSRF against a loopback address with the following check (source):
if !config.AllowLoopbackSourceAddresses && ip.IsLoopback() {
return ErrSourceAddressNotAllowed
}This check is insufficient to prevent accessing services on the local host, as services may receive traffic on 0.0.0.0. Go's IsLoopback (source) strictly follows the definition of loopback IPs beginning with 127. 0.0.0.0 is not blocked.
Credited to phannguyenlong, Benasin, benaubin.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
