Unencrypted FTP Service
The FTP service sends user names, passwords and file contents unencrypted, so anyone able to observe the traffic can capture credentials and data.
| Severity | Medium |
| CVSS 3.1 | 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N Open in the calculator |
| CVSS 4.0 | 8.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-319: Cleartext Transmission of Sensitive Information |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1040 Network Sniffing, T1557 Adversary-in-the-Middle |
| Category | Cryptographic Failures |
Description
The host runs an FTP service that accepts logins and file transfers without encryption. FTP sends the user name and password in plain text with the USER and PASS commands, and transfers file contents and directory listings over a separate data connection that is also unencrypted. Many FTP servers support FTPS, which adds TLS through the AUTH TLS command (explicit FTPS) or on a dedicated port, usually 990 (implicit FTPS), but unless TLS is required a client can still log in without it.
An attacker who can observe traffic between FTP clients and the server, for example from a compromised host on the same network segment or a device on the network path, can capture the credentials used and the files transferred, and can alter files in transit. Where the service is used across the internet, the traffic is exposed on every network it crosses. FTP accounts are often used by automated transfers whose passwords rarely change, and the same credentials frequently work on other systems, so a single capture can give lasting access.
The issue is identified by connecting to the service, usually on TCP port 21, and checking whether a login is accepted before TLS is negotiated; the server's response to the FEAT command shows whether AUTH TLS is offered at all. Scanners report it as FTP supporting cleartext authentication. SFTP, despite the similar name, is a different protocol that runs over SSH and is not affected.
Remediation
Replace unencrypted FTP with an encrypted protocol:
- Move transfers to SFTP (over SSH) where clients and partners support it, or to an HTTPS-based transfer service.
- Where FTP must remain, require TLS for both the login and the data connection: on vsftpd, set
ssl_enable=YES,force_local_logins_ssl=YESandforce_local_data_ssl=YES; on ProFTPD, setTLSEngine onandTLSRequired on; on IIS, set the site's FTP SSL Settings policy to Require SSL connections; on other servers, use the equivalent setting. - Change the passwords of FTP accounts that have been used over unencrypted connections, and make sure they are not used elsewhere.
- Restrict the service to the systems and partners that need it with firewall rules.
Confirm the fix by attempting to log in without TLS, which should be refused, and by checking with openssl s_client -starttls ftp or an FTPS client that encrypted logins and transfers work.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.