ssh-agent RSA authentication problem
|Description:||SSH doesn't check permissions on credential files enough so that users can trick ssh into using the credentials of other users.|
|Author:||"Secure Networks Inc." <sni@SECURENETWORKS.COM>|
|Compromise:||Trick ssh into using the credentials of another user when you login to a remote server.|
|Vulnerable Systems:||Those running ssh (setuid) on multiple-user systems where RSA authentication is being used. |
|Date:||20 January 1998 |
Date: Tue, 20 Jan 1998 15:42:15 -0700
From: "Secure Networks Inc." <sni@SECURENETWORKS.COM>
Subject: SNI-23: SSH - Vulnerability in ssh-agent
-----BEGIN PGP SIGNED MESSAGE-----
###### ## ## ######
## ### ## ##
###### ## # ## ##
## ## ### ##
###### . ## ## . ######.
Secure Networks Inc.
January 20, 1998
Vulnerability in ssh-agent
This advisory details a vulnerabily in the SSH cryptographic login
program. The vulnerability enables users to use RSA credentials
belonging to other users who use the ssh-agent program. This
vulnerability may allow an attacker on the same local host to login
to a remote server as the user utilizing SSH.
In order to avoid forcing users of RSA based authentication to go
through the trouble of retyping their pass phrase every time they wish
to use ssh, slogin, or scp, the SSH package includes a program called
ssh-agent, which manages RSA keys for the SSH program. The ssh-agent
program creates a mode 700 directory in /tmp, and then creates an
AF_UNIX socket in that directory. Later, the user runs the ssh-add
program, which adds his private key to the set of keys managed by the
ssh-agent program. When the user wishes to access a service which
permits him to log in using only his RSA key, the SSH client connects
to the AF_UNIX socket, and asks the ssh-agent program for the key.
Unfortunately, when connecting to the AF_UNIX socket, the SSH client is
running as super-user, and performs insufficient permissions checking.
This makes it possible for users to trick their SSH clients into using
credentials belonging to other users. The end result is that any user
who utilizes RSA authentication AND uses ssh-agent, is vulnerable.
Attackers can utilize this vulnerability to access remote accounts
belonging to the ssh-agent user.
When communicating with the ssh-agent program, the SSH program issues a
connect() system call as super-user to access the AF_UNIX socket. By
utilizing symbolic links, an attacker can cause the SSH program to
connect to an alternate user's AF_UNIX socket, and read their RSA
credentials. After the credentials have been read, SSH will use these
credentials to logon to the remote system as the victim.
This vulnerability effects the Unix versions of SSH ONLY.
SSH for unix versions 1.2.17 through 1.2.21 are vulnerable if installed
with default permissions. Versions of SSH prior to 1.2.17 are subject to
a similar (but different) attack.
F-Secure SSH for Unix systems prior to release 1.3.3 ARE vulnerable.
You can determine the version of SSH you are running by issuing the case
% ssh -V
Version 1.1 of the windows-based SSH client sold by Data Fellows Inc.
under the F-Secure brand name is NOT vulnerable to this attack.
Versions 1.0 and 1.0a of Mac SSH are NOT vulnerable to this attack.
If using the free non-commercial SSH distribution for Unix, administrators
are urged to upgrade to SSH 1.2.22 or later. Updated versions of the free
unix SSH can be found at ftp://ftp.cs.hut.fi/pub/ssh
F-Secure SSH version 1.3.3 fixes this security problem. If you are using
the commercial Data Fellows SSH package and you have a support contract,
you can obtain SSH version 1.3.3 from your local retailer.
Users without a support contract can obtain a diff file which fixes
this problem. This file can be obtained from:
As a temporary workaround, administrators may remove the setuid bit from
the SSH binary. This will prevent the attack from working, but will
disable a form of authentication documented as rhosts-RSA. For example,
if your SSH binary is in the /usr/local/bin directory, the following
command will remove the setuid bit from the SSH binary:
# chmod u-s /usr/local/bin/ssh
SSH is a cryptographic rsh, rlogin, and rcp replacement. SSH was
written by Tatu Ylonen <email@example.com>. For more information about the
noncommercial unix version of SSH, please see http://www.cs.hut.fi/ssh
Commercial versions of ssh are marketed by Data Fellows Inc. For
information about the F-secure ssh derivatives sold by Data Fellows Inc,
please see http://www.DataFellows.com/f-secure
This vulnerability was discovered by David Sacerdote <firstname.lastname@example.org>.
For more information regarding this advisory, contact Secure Networks
Inc. as <email@example.com>. A PGP public key is provided below if
privacy is required.
Type Bits/KeyID Date User ID
pub 1024/9E55000D 1997/01/13 Secure Networks Inc. <firstname.lastname@example.org>
Secure Networks <email@example.com>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
- -----END PGP PUBLIC KEY BLOCK-----
The contents of this advisory are Copyright (C) 1997 Secure Networks
Inc, and may be distributed freely provided that no fee is charged for
distribution, and that proper credit is given.
You can find Secure Networks papers at ftp://ftp.secnet.com/pub/papers
and advisories at ftp://ftp.secnet.com/advisories
You can browse our web site at http://www.secnet.com
You can subscribe to our security advisory mailing list by sending mail
to firstname.lastname@example.org with the line "subscribe sni-advisories"
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
The master index of all exploits is available
here (Very large file)
Or you can pick your favorite operating system:
This page is part of Fyodor's exploit
For a free program to automate scanning your network for vulnerable
hosts and services, check out my network mapping tool, nmap. Or try these Insecure.Org resources: