[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-security] Vulnerability in OpenSSH 2.0 to 3.0.2
- Subject: [cobalt-security] Vulnerability in OpenSSH 2.0 to 3.0.2
- From: Michael Stauber <cobalt@xxxxxxxxxxxxxx>
- Date: Thu, 7 Mar 2002 18:09:33 +0100
- Organization: Stauber Multimedia Design
- List-id: Mailing list for users to address network security on Cobalt products. <cobalt-security.list.cobalt.com>
Hi all,
just found this on bugtraq. Time for everyone to upgrade to OpenSSH 3.1
-
-----------------------------------------------------------------------------
Pine Internet Security Advisory
-
-----------------------------------------------------------------------------
Advisory ID : PINE-CERT-20020301
Authors : Joost Pol <joost@xxxxxxx>
Issue date : 2002-03-07
Application : OpenSSH
Version(s) : All versions between 2.0 and 3.0.2
Platforms : multiple
Vendor informed : 20020304
Availability : http://www.pine.nl/advisories/pine-cert-20020301.txt
-
-----------------------------------------------------------------------------
Synopsis
A bug exists in the channel code of OpenSSH versions 2.0 - 3.0.2
Users with an existing user account can abuse this bug to
gain root privileges. Exploitability without an existing
user account has not been proven but is not considered
impossible. A malicious ssh server could also use this bug
to exploit a connecting vulnerable client.
Impact
HIGH: Existing users will gain root privileges.
Description
Simple off by one error. Patch included.
Solution
The OpenSSH project will shortly release version 3.1.
Upgrading to this version is highly recommended.
This version will be made available at http://www.openssh.com
The FreeBSD port of OpenSSH has been updated to reflect the
patches as supplied in this document.
OpenSSH CVS has been updated, see
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ \
channels.c.diff?r1=1.170&r2=1.171
Or apply the attached patch as provided by PINE Internet:
http://www.pine.nl/advisories/pine-cert-20020301.patch
--
With best regards,
Michael Stauber
mstauber@xxxxxxxxxxxxxx
Unix/Linux Support Engineer