From openpkg@openpkg.org Wed May 5 18:06:14 2004 From: OpenPKG To: full-disclosure@lists.netsys.com Date: Wed, 5 May 2004 16:25:57 +0200 Subject: [Full-Disclosure] [OpenPKG-SA-2004.019] OpenPKG Security Advisory (kolab) -----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.019 05-May-2004 ________________________________________________________________________ Package: kolab Vulnerability: information leakage, privilege escalation OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= kolab-20040426-20040426 >= kolab-20040503-20040503 <= perl-kolab-5.8.4-20040503 >= perl-kolab-5.8.4-20040505 OpenPKG 2.0 <= kolab-20040217-2.0.1 >= kolab-20040217-2.0.2 <= perl-kolab-5.8.3-2.0.1 >= perl-kolab-5.8.3-2.0.2 OpenPKG 1.3 none N.A. Dependent Packages: none Description: Luca Villani reported [1] the disclosure of critical configuration information within Kolab [2], the KDE Groupware server. The affected versions store OpenLDAP passwords in plain text. The heart of Kolab is an engine written in Perl that rewrites configuration for certain applications based on templates. OpenPKG packages come with both the genuine and a modular replacement engine, both creating wrong permissions. The genuine engine is part of the "kolab" package and the replacement engine is a module in the "perl-kolab" package. The build() function in both engines left slapd.conf world-readable exhibiting the OpenLDAP "rootpw". Please check whether you are affected by running "/bin/rpm -q kolab". If you have the "kolab" 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], fetch it from the OpenPKG FTP service [6] or a mirror location, verify its integrity [7], 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 kolab-20040217-2.0.2.src.rpm ftp> bye $ /bin/openpkg rpm -v --checksig kolab-20040217-2.0.2.src.rpm $ /bin/openpkg rpm --rebuild kolab-20040217-2.0.2.src.rpm $ su - # /bin/openpkg rpm -Fvh /RPM/PKG/kolab-20040217-2.0.2.*.rpm ________________________________________________________________________ References: [1] http://www.kolab.org/pipermail/kolab-users/2004-April/000215.html [2] http://www.kolab.org/ [3] http://www.openpkg.org/tutorial.html#regular-source [4] http://www.openpkg.org/tutorial.html#regular-binary [5] ftp://ftp.openpkg.org/release/2.0/UPD/kolab-20040217-2.0.2.src.rpm [6] ftp://ftp.openpkg.org/release/2.0/UPD/ [7] 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 iD8DBQFAmPlfgHWT4GPEy58RAmh1AJ0UgFibDQE9uk64FmjgUe9o86goMgCgxtby xBmfRHC1CpRnUPaZJntQMpg= =1G7c -----END PGP SIGNATURE----- _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html