Full Disclosure mailing list archives
[OpenPKG-SA-2004.013] OpenPKG Security Advisory (cvs)
From: OpenPKG <openpkg () openpkg org>
Date: Wed, 14 Apr 2004 20:35:49 +0200
-----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-2004.013 14-Apr-2004 ________________________________________________________________________ Package: cvs Vulnerability: remote code execution OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= cvs-1.12.6-20040413 >= cvs-1.12.7-20040414 OpenPKG 2.0 <= cvs-1.12.5-2.0.0 >= cvs-1.12.5-2.0.1 OpenPKG 1.3 <= cvs-1.12.1-1.3.3 >= cvs-1.12.1-1.3.4 Dependent Packages: none Description: Sebastian Krahmer from the SuSE Security Team discovered [1] a flaw in Concurrent Versions System (CVS) [0] clients where RCS "diff files" can create files with absolute pathnames. An attacker could create a fake malicious CVS server that would cause arbitrary files to be created or overwritten when a victim connects to it. The Common Vulnerabilities and Exposures (CVE) project assigned the id CAN-2004-0180 [2] to the problem. Please check whether you are affected by running "<prefix>/bin/rpm -q cvs". If you have the "cvs" 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 most recent release OpenPKG 2.0, perform the following operations to permanently fix the security problem (for other releases adjust accordingly). $ ftp ftp.openpkg.org ftp> bin ftp> cd release/2.0/UPD ftp> get cvs-1.12.5-2.0.1.src.rpm ftp> bye $ <prefix>/bin/openpkg rpm -v --checksig cvs-1.12.5-2.0.1.src.rpm $ <prefix>/bin/openpkg rpm --rebuild cvs-1.12.5-2.0.1.src.rpm $ su - # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/cvs-1.12.5-2.0.1.*.rpm ________________________________________________________________________ References: [0] http://www.cvshome.org/ [1] http://www.suse.com/de/security/2004_08_cvs.html [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0180 [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.3/UPD/cvs-1.12.1-1.3.4.src.rpm [6] ftp://ftp.openpkg.org/release/2.0/UPD/cvs-1.12.5-2.0.1.src.rpm [7] ftp://ftp.openpkg.org/release/1.3/UPD/ [8] ftp://ftp.openpkg.org/release/2.0/UPD/ [9] http://www.openpkg.org/security.html#signature ________________________________________________________________________ For security reasons, this advisory was digitally signed with the OpenPGP public key "OpenPKG <openpkg () openpkg 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 () openpkg org> iD8DBQFAfYRYgHWT4GPEy58RArpMAKDMgxz5dlP8Y6CsGehQdBSWslDPrACgmqwK 7Q7IuwFb556bhWZ7QD+LBbo= =7pJi -----END PGP SIGNATURE----- _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- [OpenPKG-SA-2004.013] OpenPKG Security Advisory (cvs) OpenPKG (Apr 14)