From openpkg@openpkg.org Sun Mar 16 00:38:56 2003 From: OpenPKG To: bugtraq@securityfocus.com Date: Fri, 14 Mar 2003 22:30:08 +0100 Subject: [OpenPKG-SA-2003.018] OpenPKG Security Advisory (qpopper) -----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.018 14-Mar-2003 ________________________________________________________________________ Package: qpopper Vulnerability: remote code execution OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= qpopper-4.0.4-20030226 >= qpopper-4.0.5-20030313 OpenPKG 1.2 <= qpopper-4.0.4-1.2.0 >= qpopper-4.0.4-1.2.1 OpenPKG 1.1 <= qpopper-4.0.4-1.1.1 >= qpopper-4.0.4-1.1.2 Dependent Packages: none Description: According to Florian Heinz [0] a remote code execution vulnerability exists in the QPopper POP3 server [1]. Attackers may remotely exploit this vulnerability to execute arbitrary code under the user id of a mailbox owner and the "mail" group id. Please check whether you are affected by running "/bin/rpm -q qpopper". If you have the "qpopper" package installed and its version is affected (see above), we recommend that you immediately upgrade it (see Solution). [2][3] Solution: Select the updated source RPM appropriate for your OpenPKG release [4][5], fetch it from the OpenPKG FTP service [6][7] or a mirror location, verify its integrity [8], build a corresponding binary RPM from it [2] and update your OpenPKG installation by applying the binary RPM [3]. 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 qpopper-4.0.4-1.2.1.src.rpm ftp> bye $ /bin/rpm -v --checksig qpopper-4.0.4-1.2.1.src.rpm $ /bin/rpm --rebuild qpopper-4.0.4-1.2.1.src.rpm $ su - # /bin/rpm -Fvh /RPM/PKG/qpopper-4.0.4-1.2.1.*.rpm ________________________________________________________________________ References: [0] http://www.securityfocus.com/archive/1/314643/2003-03-04/2003-03-10/0 [1] http://www.eudora.com/qpopper/ [2] http://www.openpkg.org/tutorial.html#regular-source [3] http://www.openpkg.org/tutorial.html#regular-binary [4] ftp://ftp.openpkg.org/release/1.1/UPD/qpopper-4.0.4-1.1.2.src.rpm [5] ftp://ftp.openpkg.org/release/1.2/UPD/qpopper-4.0.4-1.2.1.src.rpm [6] ftp://ftp.openpkg.org/release/1.1/UPD/ [7] ftp://ftp.openpkg.org/release/1.2/UPD/ [8] 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 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 iD8DBQE+ckkwgHWT4GPEy58RAosEAJ9ROxlBdCptZ096uBg1KF9eaFw6oQCgy7gT uzDTkM+4oxfNfMVrF0U+kcA= =NNhb -----END PGP SIGNATURE-----