OpenBSD Journal

Authentication Vulnerability in OpenSSH 2.3.1

Contributed by Dengue on from the pay-attention-to-this dept.

Users of -current between January 18th and February 18th, Upgrade OpenSSH 2.3.1 to OpenSSH 2.3.2

*note*: this article has been updated to more correctly represent the facts 

OpenSSH-2.3.1, a development snapshot, only checked if a public key
for public key authentication was permitted.  In the protocol 2 part
of the server, the challenge-response step that ensures that the
connecting client is in possession of the corresponding private key
has been omitted. As a result, anyone who could obtain the public key
listed in the users authorized_keys file could log in as that user
without authentication.

A fix for this problem was committed on Februrary 8th.  The problem
was introduced on January 18th.  This is a three week time window.
Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (devel snapshot)
 


----------------------------------------------------------------------------
                
                        OpenBSD Security Advisory
        
                            February 8, 2001

             Authentication By-Pass Vulnerability in OpenSSH-2.3.1

----------------------------------------------------------------------------

SYNOPSIS

OpenSSH-2.3.1, a development snapshot, only checked if a public key
for public key authentication was permitted.  In the protocol 2 part
of the server, the challenge-response step that ensures that the
connecting client is in possession of the corresponding private key
has been omitted. As a result, anyone who could obtain the public key
listed in the users authorized_keys file could log in as that user
without authentication.

A fix for this problem was committed on Februrary 8th.  The problem
was introduced on January 18th.  This is a three week time window.

----------------------------------------------------------------------------

AFFECTED SYSTEMS

This vulnerability affects only OpenSSH version 2.3.1 with support for
protocol 2 enabled.  The latest official release OpenSSH 2.3.0 is not
affected by this problem.  The latest snapshot version OpenSSH 2.3.2
is not affected either.

----------------------------------------------------------------------------

RESOLUTION

If you installed the OpenSSH 2.3.1 development snapshot, install the
latest snapshot.  Currently, the latest snapshot is OpenSSH 2.3.2 which
is available via http://www.openssh.com/.

----------------------------------------------------------------------------
For Further information: [CORE SDI ADVISORY] SSH1 CRC-32 compensation attack detector vulnerability

(Comments are closed)

Comments

  1. By proof () proof at xcheese org on http://www.xcheese.org/~proof

    Not to be rude or un-thankful or anything.. but is OpenSSH worth the security risk? It seems to have been plauged by problems. Anyone know about the status of the code?

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]