From openpkg@openpkg.org Sat May 17 06:26:32 2003 From: OpenPKG To: bugtraq@securityfocus.com Date: Fri, 16 May 2003 11:41:59 +0200 Subject: [OpenPKG-SA-2003.029] OpenPKG Security Advisory (gnupg) -----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.029 16-May-2003 ________________________________________________________________________ Package: gnupg Vulnerability: incorrect key validation OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= gnupg-1.2.1-20030408 >= gnupg-1.2.2-20030501 OpenPKG 1.2 <= gnupg-1.2.1-1.2.0 >= gnupg-1.2.1-1.2.1 OpenPKG 1.1 <= gnupg-1.0.7-1.1.0 >= gnupg-1.0.7-1.1.1 Dependent Packages: none Description: The GNU Privacy Guard (GnuPG) [0] development team discovered [1] that the key validation code in GnuPG 1.2.1 and older versions does not properly determine the validity of keys with multiple user IDs and assigns the greatest validity of the most valid user ID, which prevents GnuPG from warning the encrypting user when a user ID does not have a trusted path. The Common Vulnerabilities and Exposures (CVE) project assigned the id CAN-2003-0255 [2] to the problem. Please check whether you are affected by running "/bin/rpm -q gnupg". If you have the "gnupg" 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 gnupg-1.2.1-1.2.1.src.rpm ftp> bye $ /bin/rpm -v --checksig gnupg-1.2.1-1.2.1.src.rpm $ /bin/rpm --rebuild gnupg-1.2.1-1.2.1.src.rpm $ su - # /bin/rpm -Fvh /RPM/PKG/gnupg-1.2.1-1.2.1.*.rpm ________________________________________________________________________ References: [0] http://www.gnupg.org/ [1] http://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000268.html [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0255 [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.2/UPD/gnupg-1.2.1-1.2.1.src.rpm [6] ftp://ftp.openpkg.org/release/1.1/UPD/gnupg-1.0.7-1.1.1.src.rpm [7] ftp://ftp.openpkg.org/release/1.2/UPD/ [8] ftp://ftp.openpkg.org/release/1.1/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 iD8DBQE+xLGPgHWT4GPEy58RAoFQAKDxdRNPzG9PB8F0YX33WpOSmPG+IACeJGx4 YY3l/yqBcbWF9S4RM72IM7I= =IkHZ -----END PGP SIGNATURE-----