First published: Thu May 13 1999(Updated: )
SSH server (sshd2) before 2.0.12 does not properly record login attempts if the connection is closed before the maximum number of tries, allowing a remote attacker to guess the password without showing up in the audit logs.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SSH (Secure Shell) | =2.0.3 | |
SSH (Secure Shell) | =2.0.8 | |
SSH (Secure Shell) | =2.0.11 | |
SSH (Secure Shell) | =2.0.9 | |
SSH (Secure Shell) | =2.0 | |
SSH (Secure Shell) | =2.0.5 | |
SSH (Secure Shell) | =2.0.6 | |
SSH (Secure Shell) | =2.0.4 | |
SSH (Secure Shell) | =2.0.1 | |
SSH (Secure Shell) | =2.0.10 | |
SSH (Secure Shell) | =2.0.7 | |
SSH (Secure Shell) | =2.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-1999-1029 is considered a high severity vulnerability due to its potential to allow unauthorized access through password guessing without audit logging.
To fix CVE-1999-1029, upgrade the SSH (Secure Shell) server to version 2.0.12 or later.
CVE-1999-1029 affects SSH server versions 2.0 through 2.0.11.
Yes, CVE-1999-1029 can be exploited remotely by attackers attempting to guess passwords without being logged.
CVE-1999-1029 allows attackers to perform brute force password guessing attacks without detection in audit logs.