[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20030319150345.GA26428@en4.engelschall.com>
Date: Wed, 19 Mar 2003 16:03:45 +0100
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2003.024] OpenPKG Security Advisory (ircii)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
openpkg-security@...npkg.org openpkg@...npkg.org
OpenPKG-SA-2003.024 19-Mar-2003
________________________________________________________________________
Package: ircii
Vulnerability: buffer overflow vulnerability
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= ircii-20030314-20030315 >= ircii-20030315-20030316
OpenPKG 1.2 <= ircii-20021103-1.2.0 >= ircii-20021103-1.2.1
OpenPKG 1.1 <= ircii-20020403-1.1.0 >= ircii-20020403-1.1.1
Dependent Packages: none
Description:
Timo Sirainen audited ircII based clients [1] and found some buffer
overflow vulnerabilities in ircii-20020912 [2]. According to his
report these problems were fixed in ircii-20030313. We have backported
the security relevant pieces of the more recent ircii-20030315 vendor
changes into releases used by OpenPKG.
Please check whether you are affected by running "<prefix>/bin/rpm -q
ircii". If you have the "ircii" package installed and its version is
affected (see above), we recommend that you immediately upgrade it
(see Solution). [3][4]
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
location, verify its integrity [9], build a corresponding binary RPM
from it [3] and update your OpenPKG installation by applying the
binary RPM [4]. For the current release OpenPKG 1.2, 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.2/UPD
ftp> get ircii-20021103-1.2.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig ircii-20021103-1.2.1.src.rpm
$ <prefix>/bin/rpm --rebuild ircii-20021103-1.2.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/ircii-20021103-1.2.1.*.rpm
________________________________________________________________________
References:
[1] http://www.securityfocus.com/archive/1/315057
[2] http://www.irchelp.org/irchelp/ircii/
[3] http://www.openpkg.org/tutorial.html#regular-source
[4] http://www.openpkg.org/tutorial.html#regular-binary
[5] ftp://ftp.openpkg.org/release/1.1/UPD/ircii-20020403-1.1.1.src.rpm
[6] ftp://ftp.openpkg.org/release/1.2/UPD/ircii-20021103-1.2.1.src.rpm
[7] ftp://ftp.openpkg.org/release/1.1/UPD/
[8] ftp://ftp.openpkg.org/release/1.2/UPD/
[9] http://www.openpkg.org/security.html#signature
________________________________________________________________________
For security reasons, this advisory was digitally signed with
the OpenPGP public key "OpenPKG <openpkg@...npkg.org>" (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 <openpkg@...npkg.org>
iD8DBQE+eIZngHWT4GPEy58RAleYAJ4xmlL78sJFnmZ48XONR3NCTcxOTwCgrShv
PO52bUXnK9qzPMon2U9TXvo=
=Vnet
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists