Technical impact
The Erlang/OTP ftp module contains an SSRF flaw because the PASV handler accepts the IP address from a 227 response without validating it against the control connection’s peer address. An attacker controlling or compromising an FTP server can cause the client to establish a data connection to an arbitrary internal or external host and port, allowing read or write access to that host. This enables internal reconnaissance, data exfiltration, or FTP bounce attacks against third‑party servers. The issue exists in the default passive mode configuration (mode=passive, ipfamily=inet, ftp_extension=false) and is not mitigated by the EPSV handlers, which correctly derive the IP from the control connection. RFC 2577 recommends validating the PASV response IP, but the current implementation does not.
Affected Systems
Erlang/OTP versions before 29.0.2, including OTP 28.5.0.2 and 27.3.4.13, contain the vulnerable ftp_internal module. The issue spans inets releases 5.10.4 through 6.5 and ftp releases 1.0 to 1.2.6, 1.2.4.1 and 1.2.3.1. The ftp application is deprecated and will be removed in OTP‑30, so newer OTP releases are safe.
Risk and Exploitability
The CVSS base score is 6.3, indicating moderate risk. EPSS is < 1%, reflecting a very low but non‑zero exploitation probability, and the vulnerability is not listed in CISA KEV. An attacker with access to an FTP server that can send a crafted 227 response can cause the client to connect to a chosen IP and port, facilitating internal reconnaissance or data exfiltration. No special authentication is required; the attack occurs during normal FTP use.
Debian DSA