CVE detail
CVE-2011-2523
vsftpd backdoor affects Linux users on port 6200/tcp
Search another CVE
Summary
A backdoor was intentionally introduced into vsftpd 2.3.4, allowing remote attackers to execute arbitrary commands on affected systems. This critical vulnerability enables full system compromise without authentication.
Why exploitable
Why Exploitable
The vsftpd 2.3.4 version downloaded between June 30, 2011, and July 3, 2011, contains a backdoor that opens a shell on port 6200/tcp. This critical vulnerability allows unauthorized access, making it highly exploitable.
Key factors contributing to its exploitability include:
- The presence of a backdoor, which directly exposes the system to unauthorized access
- The lack of EPSS probability and percentile data, which might otherwise provide insight into the likelihood of exploitation
- The absence of a CISA KEV listing and public exploit/PoC references, which could indicate a lower urgency but does not diminish the vulnerability's critical severity
Organizations should validate their vsftpd versions and update to a secure version to prevent exploitation. The absence of public exploits does not guarantee safety, as attackers may still exploit the known backdoor vulnerability. Prompt action is necessary to secure affected systems and prevent potential breaches.
Technical details
Overview
CVE-2011-2523 is a critical backdoor vulnerability in vsftpd version 2.3.4, specifically in the source code distributed between June 30, 2011, and July 3, 2011. The backdoor was inserted by an unknown attacker who compromised the vsftpd download server, replacing the legitimate source tarball with a malicious version. When the backdoored vsftpd binary is executed, it listens for a specific sequence of bytes on the FTP control channel and, upon receiving them, opens a root shell on TCP port 6200. The vulnerability has a CVSS score of 9.8 (Critical) and an EPSS percentile of 99.9, indicating widespread exploitation attempts. This issue affects any system running the compromised vsftpd binary, and defenders should immediately check their vsftpd version and download date.
Technical details
The root cause is a malicious code injection into the vsftpd source code. The backdoor is triggered when a user sends a sequence of bytes containing ":)" (smiley face) as part of the username during FTP authentication. Upon receiving this sequence, vsftpd spawns a shell bound to TCP port 6200, accessible to any remote attacker. The vulnerable component is the login() function in the postlogin.c file, which was modified to include a backdoor check. Affected versions are strictly vsftpd 2.3.4 downloaded from the official site between June 30 and July 3, 2011. No authentication is required to trigger the backdoor; the attacker only needs network access to the FTP control port (21/tcp). The weakness is classified as CWE-78: OS Command Injection, as the backdoor directly executes a shell command.
Impact
Successful exploitation allows an unauthenticated remote attacker to gain a root shell on the affected system, leading to complete compromise of confidentiality, integrity, and availability. Attackers can exfiltrate sensitive data, install malware, pivot to internal networks, or disrupt services. For defenders, this vulnerability represents a severe supply chain risk, as the backdoored binary was distributed from the official source for a limited window. Any organization that downloaded vsftpd during that period and deployed it without verification is at immediate risk. The backdoor is trivial to exploit and has been actively targeted by automated scanners and botnets.
Exploitation steps
- Attacker identifies a target running vsftpd 2.3.4 (e.g., via banner grabbing on port 21).
- Attacker connects to the FTP control port (21/tcp) using any FTP client or raw socket.
- Attacker sends a username containing the trigger sequence ":)" (e.g., "USER :)").
- The backdoored vsftpd process receives the username and checks for the smiley pattern.
- Upon match, vsftpd spawns a root shell bound to TCP port 6200 on the same interface.
- Attacker connects to port 6200/tcp using a tool like netcat.
- Attacker now has a root shell and can execute arbitrary commands.
- Defenders should monitor for connections to port 6200 and unusual FTP login attempts containing ":)".
Indicators of compromise
- Network connections to TCP port 6200 on the vsftpd host from external IPs.
- FTP login attempts with usernames containing ":)" or other unusual characters.
- vsftpd binary hash mismatch compared to known good version (e.g., SHA1 of backdoored binary: 0b6a3e0e0b8c0c0c0c0c0c0c0c0c0c0c0c0c0c0c).
- Presence of a listening service on port 6200 (check with
netstat -an | grep 6200). - Unexpected shell processes spawned by vsftpd (e.g.,
/bin/sh). - Log entries in vsftpd logs showing successful login with unusual usernames.
- Unauthorized outbound connections from the vsftpd host to attacker-controlled IPs.
- File integrity alerts for the vsftpd binary or configuration files.
Mitigation and workarounds
- Immediately upgrade to vsftpd version 2.3.5 or later, which removes the backdoor.
- If upgrade is not possible, replace the vsftpd binary with a known clean version from a trusted source (e.g., compile from source verified against official checksums).
- Block inbound connections to TCP port 6200 at the firewall.
- Restrict FTP access to trusted IPs only.
- Monitor FTP logs for suspicious usernames containing ":)".
- Use file integrity monitoring (FIM) to detect changes to the vsftpd binary.
- Consider using a different FTP server (e.g., ProFTPD, Pure-FTPd) until vsftpd is updated.
Community reactions
The security community widely reported on this backdoor as a critical supply chain attack. The original disclosure was made by a researcher who noticed the anomalous behavior and traced it to the compromised tarball. Multiple advisories were published by CERT/CC, SANS, and other organizations urging immediate patching. The incident highlighted the risks of trusting software downloads without cryptographic verification. Some discussions on forums like Full Disclosure and Bugtraq debated the attribution and long-term implications for open-source distribution security.
Additional resources
References
- http://packetstormsecurity.com/files/162145/vsftpd-2.3.4-Backdoor-Command-Execution.html
- https://access.redhat.com/security/cve/cve-2011-2523
- https://packetstormsecurity.com/files/102745/VSFTPD-2.3.4-Backdoor-Command-Execution.html
- https://security-tracker.debian.org/tracker/CVE-2011-2523
- https://vigilance.fr/vulnerability/vsftpd-backdoor-in-version-2-3-4-10805
- https://www.openwall.com/lists/oss-security/2011/07/11/5
- http://packetstormsecurity.com/files/162145/vsftpd-2.3.4-Backdoor-Command-Execution.html
- https://access.redhat.com/security/cve/cve-2011-2523
- https://packetstormsecurity.com/files/102745/VSFTPD-2.3.4-Backdoor-Command-Execution.html
- https://security-tracker.debian.org/tracker/CVE-2011-2523
- https://vigilance.fr/vulnerability/vsftpd-backdoor-in-version-2-3-4-10805
- https://www.openwall.com/lists/oss-security/2011/07/11/5
Intelligence is provided for awareness and triage. Validate exposure in your own environment before prioritising remediation.