CVE-1999-1138: Critical severity SCO UNIX vulnerability
SCO UNIX System V/386 Release 3.2, and other SCO products, installs the home directories (1) /tmp for the dos user, and (2) /usr/tmp for the asg user, which allows other users to gain access to those accounts since /tmp and /usr/tmp are world-writable.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Change the home directory for the 'dos' user so it is not set to /tmp. Move the user's home to a non-world-writable path, set ownership to the 'dos' user, and restrict permissions so other users cannot access the account files.
User account 'dos' home_directory = do not use /tmp - Configuration
Change the home directory for the 'asg' user so it is not set to /usr/tmp. Move the user's home to a non-world-writable path, set ownership to the 'asg' user, and restrict permissions so other users cannot access the account files.
User account 'asg' home_directory = do not use /usr/tmp - Configuration
Do not use world-writable directories (/tmp or /usr/tmp) as user home directories. Adjust ownership and permissions on /tmp and /usr/tmp to prevent unauthorized access to user account files; if these directories must remain world-writable for other purposes, ensure they are not assigned as home directories and apply appropriate restrictive controls (e.g., sticky bit and ownership) so one user cannot gain access to another user's files.
/tmp and /usr/tmp permissions = not world-writable for use as home directories / restrict access
Event History
Frequently Asked Questions
What is the severity of CVE-1999-1138?
CVE-1999-1138 is classified as a high severity vulnerability due to its ability to allow unauthorized access to user accounts.
How do I fix CVE-1999-1138?
To mitigate CVE-1999-1138, ensure that the /tmp and /usr/tmp directories are not set to be world-writable.
What products are affected by CVE-1999-1138?
CVE-1999-1138 affects SCO UNIX System V/386 Release 3.2 and various versions of SCO Open Desktop and OpenServer.
What are the risks associated with CVE-1999-1138?
The main risk of CVE-1999-1138 is that other users can gain unauthorized access to sensitive data in the home directories of affected accounts.
Is there a workaround for CVE-1999-1138?
A possible workaround for CVE-1999-1138 is to change the permissions of the /tmp and /usr/tmp directories to prevent public access.