Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-0080: Certain configurations of wu-ftp FTP server 2.4 use a _PATH_EXECPATH setting to a directory with dan

0
High
VulnerabilityCVE-1999-0080cve-1999-0080
Published: Thu Nov 30 1995 (11/30/1995, 05:00:00 UTC)
Source: NVD
Vendor/Project: washington_university
Product: wu-ftpd

Description

Certain configurations of wu-ftp FTP server 2.4 use a _PATH_EXECPATH setting to a directory with dangerous commands, such as /bin, which allows remote authenticated users to gain root access via the "site exec" command.

AI-Powered Analysis

AILast updated: 07/01/2025, 15:55:54 UTC

Technical Analysis

CVE-1999-0080 is a critical vulnerability affecting certain configurations of the wu-ftp FTP server version 2.4, developed by Washington University. The vulnerability arises when the server's _PATH_EXECPATH setting points to a directory containing dangerous system commands, such as /bin. This misconfiguration allows remote attackers who have authenticated access to the FTP server to execute arbitrary commands with root privileges via the "site exec" command. The "site exec" command is an FTP protocol extension that permits execution of server-side commands. Because the _PATH_EXECPATH is set to a directory with system binaries, an attacker can leverage this to run any command as the root user, leading to full system compromise. The vulnerability has a CVSS score of 10, indicating maximum severity, with network attack vector, no authentication required, and complete impact on confidentiality, integrity, and availability. Although the vulnerability was published in 1995 and no patches are available, it remains a critical risk in legacy systems still running this outdated FTP server version. Exploitation does not require user interaction, and the attack surface is broad as it can be triggered remotely over the network. The lack of known exploits in the wild may be due to the obsolescence of wu-ftpd 2.4, but any remaining deployments are at extreme risk of compromise if exposed.

Potential Impact

For European organizations, the impact of this vulnerability is severe if legacy systems running wu-ftpd 2.4 are still in use, especially in critical infrastructure, government, or industrial environments where FTP servers may be part of legacy file transfer workflows. Successful exploitation leads to full root access, allowing attackers to steal sensitive data, disrupt operations, implant persistent malware, or pivot to other internal systems. This could result in data breaches, operational downtime, regulatory non-compliance (e.g., GDPR violations due to data exposure), and reputational damage. Given the high severity and ease of exploitation, any exposed vulnerable FTP server represents a critical entry point for attackers targeting European organizations. The threat is exacerbated by the fact that no patches exist, so mitigation relies on configuration changes or decommissioning the vulnerable software. Organizations with legacy systems in sectors such as manufacturing, energy, or public administration are particularly at risk due to the potential for targeted attacks and the strategic importance of these sectors in Europe.

Mitigation Recommendations

Since no patches are available for wu-ftpd 2.4, European organizations should take immediate steps to mitigate this vulnerability. First, identify and inventory all systems running wu-ftpd 2.4 or similar legacy FTP servers. Disable or decommission these servers if they are no longer necessary. If the FTP service is required, replace wu-ftpd with a modern, actively maintained FTP server that does not have this vulnerability. For systems that must continue running wu-ftpd 2.4, reconfigure the _PATH_EXECPATH setting to point to a directory that does not contain dangerous system binaries, or disable the "site exec" command entirely to prevent remote command execution. Additionally, restrict FTP access using network-level controls such as firewalls and VPNs to limit exposure to trusted users only. Implement strong authentication and monitoring to detect any unauthorized access attempts. Regularly audit FTP server configurations and logs to identify suspicious activity. Finally, consider migrating file transfer workflows to more secure protocols such as SFTP or FTPS, which provide encryption and stronger authentication mechanisms.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32ab6fd31d6ed7de49a

Added to database: 5/20/2025, 3:43:38 PM

Last enriched: 7/1/2025, 3:55:54 PM

Last updated: 2/7/2026, 5:54:28 PM

Views: 30

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats