CVE-2002-1711 in Basilix
Summary
by MITRE
BasiliX 1.1.0 saves attachments in a world readable /tmp/BasiliX directory, which allows local users to read other users attachments.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 09/02/2025
The vulnerability identified as CVE-2002-1711 affects BasiliX version 1.1.0, a web-based email client application that handles email attachments and user data. This security flaw represents a critical misconfiguration in the application's file system permissions and temporary file handling mechanisms. The vulnerability stems from the application's improper handling of temporary file storage, specifically the creation of a world-readable directory structure that exposes sensitive user attachments to unauthorized access.
The technical implementation of this vulnerability involves the creation of a temporary directory at /tmp/BasiliX with overly permissive permissions that allow any local user to read files stored within this location. This represents a classic case of inadequate access control and privilege separation within the application's temporary file management system. The flaw occurs during the attachment processing phase when the application stores incoming email attachments in the /tmp directory without proper permission controls or user isolation mechanisms. This design flaw directly violates fundamental security principles of least privilege and proper resource management, creating an information disclosure vulnerability that affects all users of the system.
The operational impact of this vulnerability is significant as it enables local users to access attachments belonging to other users who have processed emails through the vulnerable BasiliX application. This creates a serious privacy breach where sensitive information contained in email attachments could be accessed by any local user with read permissions on the temporary directory. The vulnerability affects the confidentiality aspect of the CIA triad and can lead to unauthorized data access, potential information leakage, and violation of user privacy expectations. Attackers could exploit this by simply navigating to the temporary directory and reading the stored attachments, which may contain personal information, business documents, or other sensitive materials. This type of vulnerability is particularly dangerous in multi-user environments where users may not be fully trusted or where system administrators have not properly configured user isolation mechanisms.
The vulnerability aligns with CWE-732, which describes improper permission assignment for critical resources, and represents a failure to implement proper access control measures for temporary file storage. From an attack perspective, this vulnerability can be classified under the ATT&CK technique T1005, which involves data from local system repositories, and T1041, which involves data compression and encryption. The exploitation requires minimal technical skill and can be automated, making it particularly dangerous. Organizations should implement proper file permission controls, ensure that temporary directories are created with restrictive permissions, and consider implementing proper user isolation mechanisms. The recommended mitigations include setting appropriate directory permissions, using secure temporary file creation methods, and implementing proper access control lists for temporary storage locations. Additionally, system administrators should regularly audit temporary file directories for proper permissions and consider implementing monitoring solutions to detect unauthorized access attempts to sensitive temporary storage areas.