SSH1 with encryption disabled could allow client authentication to be forwarded
|ssh-authentication-forwarding (6603)||Medium Risk|
SSH (Secure Shell) with encryption disabled could allow client authentication to be forwarded if the client allows unknown host keys. An attacker can obtain a client's public host key during a connection attempt and use it to open and authenticate an SSH session to another server with the same access rights as the victim.
Upgrade to the latest version of SSH (2.4.0 or later), available from the SSH Secure Shell Download Page. See References.
- SSH Communications Security Web site: SSH1 vulnerabilities.
- CVE-2001-1473: The SSH-1 protocol allows remote servers to conduct man-in-the-middle attacks and replay a client challenge response to a target server by creating a Session ID that matches the Session ID of the target, but which uses a public key pair that is weaker than the target's public key, which allows the attacker to compute the corresponding private key and use the target's Session ID with the compromised key pair to masquerade as the target.
- US-CERT VU#684820: SSH-1 allows client authentication to be forwarded by a malicious server to another server
- SSH SSH 1.2.24
- SSH SSH 1.2.25
- SSH SSH 1.2.26
- SSH SSH 1.2.27
- SSH SSH 1.2.28
- SSH SSH 1.2.29
- SSH SSH 1.2.30
- SSH SSH 1.2.31
Jan 18, 2001
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this