head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2005.12.03.12.19.40; author rse; state Exp; branches; next 1.3; commitid qqpAOapyuzxSmacr; 1.3 date 2005.12.03.11.50.04; author rse; state Exp; branches; next 1.2; commitid irQCXvyd7wvJcacr; 1.2 date 2003.07.10.14.51.25; author rse; state Exp; branches; next 1.1; 1.1 date 2003.07.10.09.54.17; author thl; state Exp; branches; next ; desc @@ 1.4 log @resign after latest adjustments @ text @-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ OpenPKG Security Advisory The OpenPKG Project http://www.openpkg.org/security.html http://www.openpkg.org openpkg-security@@openpkg.org openpkg@@openpkg.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 CVE-2003-0282 [2] to the problem. Please check whether you are affected by running "/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 $ /bin/rpm -v --checksig infozip-1.2.0-1.2.1.src.rpm $ /bin/rpm --rebuild infozip-1.2.0-1.2.1.src.rpm $ su - # /bin/rpm -Fvh /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=CVE-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 " (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 iD8DBQFDkYzMgHWT4GPEy58RAk6XAKC76daA/Va3pqamHgz94xGUHzqnygCfcQCu 1/+rHRYb8PBTvY1F98y5J8E= =0FKk -----END PGP SIGNATURE----- @ 1.3 log @switch to newer world order of CVE instead of CAN and where no more solution hints are specified in detail and anybody should already memorize this standard text @ text @d80 3 a82 3 iD8DBQE/DVYpgHWT4GPEy58RAisWAKCfTyhAL0ZEt7XAUArYbNLES/QQkwCghv5N AvflUCxv94iCNmCRHbk6L4g= =Ki6S @ 1.2 log @finish infozip SA @ text @d31 1 a31 1 project assigned the id CAN-2003-0282 [2] to the problem. d60 1 a60 1 [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0282 @ 1.1 log @SA-2003.033-infozip; CAN-2003-0282 @ text @d1 3 d16 1 a16 1 Affected Releases: Affected Packages: Corrected Packages: a22 17 Affected Releases: Dependent Packages: OpenPKG CURRENT bar quux OpenPKG 1.2 bar quux OpenPKG 1.1 bar FIXME candidates cvsweb PreReq: docbook BuildPreReq: heise PreReq: BuildPreReq: mozilla PreReq: BuildPreReq: pccts BuildPreReq: sam2p PreReq: BuildPreReq: sav BuildPreReq: saxon BuildPreReq: tetex BuildPreReq: tex4ht BuildPreReq: d24 8 a31 8 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. d36 1 a36 2 (see Solution) and it's dependent packages (see above), if any, too. [3][4] a55 3 Additionally, we recommend that you rebuild and reinstall all dependent packages (see above), if any, too. [3][4] d77 7 @