Date: Fri, 8 Mar 2002 10:56:26 +0100
From: OpenPKG <[email protected]>
To: [email protected]Subject: [OpenPKG-SA-2002.002] OpenPKG Security Advisory (openssh)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.htmlhttp://www.openpkg.org[email protected][email protected]
OpenPKG-SA-2002.001 08-Mar-2002
________________________________________________________________________
Package: openssh
Vulnerability: root exploit
OpenPKG Specific: no
Affected Releases: OpenPKG 1.0
Affected Packages: <= openssh-3.0.2p1-1.0.1
Corrected Packages: >= openssh-3.0.2p1-1.0.2
Dependent Packages: -
Description:
According to an OpenSSH Security Advisory [5] and the original PINE
Internet Security Advisory [6] from Joost Pol <[email protected]>,
there is an off-by-one bug in OpenSSH's channel code that could be
used by an attacker with a local account on the victim's machine
to obtain root privileges on that machine. Another scenario for
this vulnerability is that of a malicious SSH server exploiting a
vulnerable SSH client connecting to it.
Please check whether you are affected by running "<prefix>/bin/rpm -qa
openssh". If you have the "openssh" package installed and its version
is affected (see above), we recommend that you immediately upgrade
it (see Solution). Additionally, we recommend that you rebuild and
reinstall all dependent OpenPKG packages, too. [2]
Workaround:
Perform the following operations to temporarily workaround the
security problem (be careful, it deactivates the whole service):
$ su -
# <prefix>/etc/rc openssh stop
# <prefix>/bin/rpm -e openssh
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[4], fetch it from the OpenPKG FTP service [3] or a mirror location,
verify its integrity [1], build a corresponding binary RPM from it
and update your OpenPKG installation by applying the binary RPM [2].
For the latest OpenPKG 1.0 release, perform the following operations
to permanently fix the security problem (for other releases adjust
accordingly).
$ ftp ftp.openpkg.org
ftp> bin
ftp> cd release/1.0/UPD
ftp> get openssh-3.0.2p1-1.0.2.src.rpm
ftp> bye
$ <prefix>/bin/rpm --checksig openssh-3.0.2p1-1.0.2.src.rpm
$ <prefix>/bin/rpm --rebuild openssh-3.0.2p1-1.0.2.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/openssh-3.0.2p1-1.0.2.*.rpm
________________________________________________________________________
References:
[1] http://www.openpkg.org/security.html#signature
[2] http://www.openpkg.org/tutorial.html#regular-source
[3] ftp://ftp.openpkg.org/release/1.0/UPD/
[4] ftp://ftp.openpkg.org/release/1.0/UPD/openssh-3.0.2p1-1.0.2.src.rpm
[5] http://www.openbsd.org/advisories/ssh_channelalloc.txt
[6] http://www.pine.nl/advisories/pine-cert-20020301.txt
________________________________________________________________________
For security reasons, this advisory was digitally signed with
the OpenPGP public key "OpenPKG <[email protected]>" (ID 63C4CB9F)
of the OpenPKG project which you can find under the official URL
http://www.openpkg.org/openpkg.pgp or on http://keyserver.pgp.com/. To
check the integrity of this advisory, verify its digital signature by
using GnuPG (http://www.gnupg.org/). For instance, pipe this message to
the command "gpg --verify --keyserver keyserver.pgp.com".
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <[email protected]>
iEYEARECAAYFAjyIiiYACgkQgHWT4GPEy5+DrACgkSjm3y6VaFqQrtxKCU1eDYEo
RrcAn2W4B3hDbVLjHvHOaiXFeu0kjjvx
=qaL1
-----END PGP SIGNATURE-----
