CVE-1999-1345 describes a vulnerability in the Auto_FTP 0.2 software, specifically in the Auto_FTP.pl script. This script uses the directory /tmp/ftp_tmp as a shared temporary storage location with insecure permissions. Because /tmp/ftp_tmp is accessible by local users without proper access controls, it allows these users to place arbitrary files into this directory. Consequently, local users can send arbitrary files to the remote FTP server by simply placing them in /tmp/ftp_tmp, bypassing any intended restrictions or authentication mechanisms. Additionally, the insecure permissions allow local users to view files currently being transferred through this directory, potentially exposing sensitive data. The vulnerability is local in nature, requiring the attacker to have local access to the system where Auto_FTP is running. The CVSS score of 4.6 (medium severity) reflects that the attack vector is local, the attack complexity is low, no authentication is required, and the impact affects confidentiality, integrity, and availability to a limited extent. No patches are available for this vulnerability, and there are no known exploits in the wild. The root cause is the insecure permission settings on a shared temporary directory used by the script, which is a common security misconfiguration in older software. Given the age of the vulnerability (published in 1999) and the specific version affected (0.2), this issue primarily affects legacy systems still running this outdated software version.

For European organizations, the impact of this vulnerability is primarily relevant to those still operating legacy systems with Auto_FTP 0.2 installed. The vulnerability allows local attackers to manipulate files being transferred to remote servers, potentially leading to unauthorized data exfiltration or injection of malicious files. Confidentiality is compromised as local users can view files in transit, and integrity is at risk due to the ability to send arbitrary files. Availability impact is limited but possible if malicious files disrupt the FTP process. However, since exploitation requires local access, the threat is mitigated in environments with strong physical and user access controls. Organizations in sectors with legacy Unix/Linux systems or those using outdated FTP automation tools may be more vulnerable. The lack of patches means organizations must rely on compensating controls. Overall, the threat is moderate but could be significant in sensitive environments where local user access is not tightly controlled or where FTP transfers involve sensitive data.

Given that no patches are available for Auto_FTP 0.2, European organizations should consider the following specific mitigations: 1) Replace or upgrade Auto_FTP to a more recent, actively maintained FTP automation tool that does not use insecure shared directories. 2) Restrict local user access to the system running Auto_FTP to trusted administrators only, minimizing the risk of local exploitation. 3) Change the permissions on /tmp/ftp_tmp or configure Auto_FTP to use a directory with strict access controls, ensuring only the Auto_FTP process user can read/write to it. 4) Monitor the /tmp/ftp_tmp directory for unauthorized file creation or access attempts using file integrity monitoring tools. 5) Implement strict logging and auditing of FTP transfer activities to detect suspicious behavior. 6) If legacy systems must be retained, isolate them in segmented network zones with limited user access and no direct user login capability. 7) Educate system administrators about the risks of insecure temporary directories and the importance of secure file permissions in FTP automation contexts.