[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20030710120558.GA70177@en4.engelschall.com>
Date: Thu, 10 Jul 2003 14:05:58 +0200
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2003.033] OpenPKG Security Advisory (infozip)
-----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.033 10-Jul-2003
________________________________________________________________________
Package: infozip
Vulnerability: overwrite arbitrary files
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= infozip-20030306-20030708 >= infozip-20030710-20030710
OpenPKG 1.2 <= infozip-1.2.0-1.2.0 >= infozip-1.2.0-1.2.1
OpenPKG 1.1 <= infozip-1.1.0-1.1.0 >= infozip-1.1.0-1.1.1
Dependent Packages: none
Description:
A directory traversal vulnerability in UnZip 5.50 allows attackers
to overwrite arbitrary files via invalid characters between two "."
(dot) characters, which are filtered and result in a ".." sequence.
The corrected packages include a patch taken from RedHat [1] ensuring
that non-printable characters do not make it possible for a malicious
.zip file to write to parent directories unless the "-:" command line
parameter is specified. The Common Vulnerabilities and Exposures (CVE)
project assigned the id CAN-2003-0282 [2] to the problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
infozip". If you have the "infozip" 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 infozip-1.2.0-1.2.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig infozip-1.2.0-1.2.1.src.rpm
$ <prefix>/bin/rpm --rebuild infozip-1.2.0-1.2.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/infozip-1.2.0-1.2.1.*.rpm
________________________________________________________________________
References:
[1] http://rhn.redhat.com/errata/RHSA-2003-199.html
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0282
[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/infozip-1.1.0-1.1.1.src.rpm
[6] ftp://ftp.openpkg.org/release/1.2/UPD/infozip-1.2.0-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 retrieve from http://pgp.openpkg.org and
hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/
for details on how to verify the integrity of this advisory.
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg@...npkg.org>
iD8DBQE/DVYpgHWT4GPEy58RAisWAKCfTyhAL0ZEt7XAUArYbNLES/QQkwCghv5N
AvflUCxv94iCNmCRHbk6L4g=
=Ki6S
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists