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-0081: wu-ftp allows files to be overwritten via the rnfr command.

0
Medium
VulnerabilityCVE-1999-0081cve-1999-0081
Published: Sat Jan 11 1997 (01/11/1997, 05:00:00 UTC)
Source: NVD
Vendor/Project: washington_university
Product: wu-ftpd

Description

wu-ftp allows files to be overwritten via the rnfr command.

AI-Powered Analysis

AILast updated: 07/02/2025, 00:11:50 UTC

Technical Analysis

CVE-1999-0081 is a vulnerability in the wu-ftpd (Washington University FTP daemon) server software that allows an attacker to overwrite files on the server via the RNFR (rename from) FTP command. The RNFR command is part of the FTP protocol used to rename files. In this vulnerability, the wu-ftpd server does not properly validate or restrict the RNFR command, enabling an attacker to specify arbitrary files for renaming operations. This can lead to overwriting critical files on the server filesystem without authentication. The vulnerability was published in 1997 and has a CVSS score of 5.0 (medium severity), indicating that it is remotely exploitable over the network without authentication, requires low attack complexity, and impacts the integrity of the system by allowing unauthorized file modification. There is no confidentiality or availability impact reported. No patches are available for this vulnerability, and there are no known exploits in the wild currently documented. However, given the age of the vulnerability and the obsolescence of wu-ftpd in many environments, active exploitation is likely limited to legacy systems still running this FTP daemon. The vulnerability highlights the risk of using outdated FTP servers that lack modern security controls and input validation mechanisms.

Potential Impact

For European organizations, the impact of this vulnerability primarily concerns legacy systems still running wu-ftpd. Successful exploitation could allow attackers to overwrite critical files, potentially leading to defacement, insertion of malicious code, or disruption of services relying on those files. While the vulnerability does not directly affect confidentiality or availability, integrity compromise can lead to further attacks or system instability. Organizations in sectors with legacy infrastructure, such as manufacturing, utilities, or government agencies with older IT environments, may be at higher risk. Additionally, if wu-ftpd servers are exposed to the internet without proper network segmentation or monitoring, attackers could exploit this vulnerability remotely. The lack of available patches means organizations must rely on compensating controls or migration to more secure FTP solutions. Given the medium severity and no known active exploits, the immediate risk is moderate but should not be ignored, especially in environments where wu-ftpd remains in use.

Mitigation Recommendations

Since no patches are available for CVE-1999-0081, European organizations should take the following specific mitigation steps: 1) Identify and inventory all systems running wu-ftpd to assess exposure. 2) Immediately restrict network access to these FTP servers using firewalls and network segmentation to limit exposure to trusted internal networks only. 3) Disable or replace wu-ftpd with modern, actively maintained FTP server software that includes proper input validation and security features. 4) If replacement is not immediately feasible, configure the FTP server to disable or restrict the RNFR command if possible, or implement application-layer filtering to detect and block suspicious RNFR usage. 5) Monitor FTP server logs for unusual rename operations or file modifications indicative of exploitation attempts. 6) Employ host-based intrusion detection systems (HIDS) to alert on unauthorized file changes. 7) Educate system administrators about the risks of legacy FTP servers and encourage migration to secure file transfer protocols such as SFTP or FTPS. These steps go beyond generic advice by focusing on compensating controls and proactive detection in the absence of patches.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32ab6fd31d6ed7de629

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

Last enriched: 7/2/2025, 12:11:50 AM

Last updated: 2/7/2026, 12:05:53 PM

Views: 27

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