CVE-1999-1434: High severity Slackware Slackware Linux vulnerability
login in Slackware Linux 3.2 through 3.5 does not properly check for an error when the /etc/group file is missing, which prevents it from dropping privileges, causing it to assign root privileges to any local user who logs on to the server.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Ensure the /etc/group file exists on the system and is readable by the login process. Restore /etc/group from a known-good backup or copy a correct group file from a trusted installation if it is missing.
login (Slackware Linux) /etc/group presence = present - Compensating control
Until /etc/group has been restored and verified, restrict or disable local logins (console/SSH/local account access) to trusted administrators to prevent local users from obtaining elevated privileges.
- Operational
If /etc/group was missing, restore or reconstruct the file immediately (from backup or a trusted source). After restoring, verify logins behave correctly and that privilege dropping works as expected.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-1434?
CVE-1999-1434 is considered a high severity vulnerability due to its potential to grant root privileges to any local user.
How do I fix CVE-1999-1434?
To fix CVE-1999-1434, ensure that the /etc/group file exists and is properly configured.
Which versions of Slackware Linux are affected by CVE-1999-1434?
CVE-1999-1434 affects Slackware Linux versions 3.2, 3.3, 3.4, and 3.5.
What type of vulnerability is CVE-1999-1434?
CVE-1999-1434 is a privilege escalation vulnerability.
Can CVE-1999-1434 be exploited remotely?
CVE-1999-1434 is not a remote exploit, as it requires local access to the server.