Skip to content

imgproxy is vulnerable to SSRF against 0.0.0.0

Moderate severity GitHub Reviewed Published Jan 27, 2025 in imgproxy/imgproxy • Updated Jan 27, 2025

Package

gomod github.com/imgproxy/imgproxy (Go)

Affected versions

< 3.27.2

Patched versions

3.27.2

Description

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.

References

@DarthSim DarthSim published to imgproxy/imgproxy Jan 27, 2025
Published by the National Vulnerability Database Jan 27, 2025
Published to the GitHub Advisory Database Jan 27, 2025
Reviewed Jan 27, 2025
Last updated Jan 27, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2025-24354

GHSA ID

GHSA-j2hp-6m75-v4j4

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.