OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 05-May-2004 15:18:56
Branch: HEAD Handle: 2004050514185501
Added files:
openpkg-web/security OpenPKG-SA-2004.019-kolab.txt
Modified files:
openpkg-web security.txt security.wml
Log:
SA-2004.019-kolab
Summary:
Revision Changes Path
1.75 +1 -0 openpkg-web/security.txt
1.95 +1 -0 openpkg-web/security.wml
1.1 +79 -0 openpkg-web/security/OpenPKG-SA-2004.019-kolab.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/security.txt
============================================================================
$ cvs diff -u -r1.74 -r1.75 security.txt
--- openpkg-web/security.txt 3 May 2004 08:42:55 -0000 1.74
+++ openpkg-web/security.txt 5 May 2004 13:18:55 -0000 1.75
@@ -1,3 +1,4 @@
+05-May-2004: Security Advisory: S<OpenPKG-SA-2004.019-kolab>
30-Apr-2004: Security Advisory: S<OpenPKG-SA-2004.018-proftpd>
29-Apr-2004: Security Advisory: S<OpenPKG-SA-2004.017-png>
16-Apr-2004: Security Advisory: S<OpenPKG-SA-2004.016-neon>
@@ .
patch -p0 <<'@@ .'
Index: openpkg-web/security.wml
============================================================================
$ cvs diff -u -r1.94 -r1.95 security.wml
--- openpkg-web/security.wml 3 May 2004 08:42:55 -0000 1.94
+++ openpkg-web/security.wml 5 May 2004 13:18:55 -0000 1.95
@@ -76,6 +76,7 @@
</define-tag>
<box bdwidth=1 bdcolor="#a5a095" bdspace=10 bgcolor="#e5e0d5">
<table cellspacing=0 cellpadding=0 border=0>
+ <sa 2004.019 kolab>
<sa 2004.018 proftpd>
<sa 2004.017 png>
<sa 2004.016 neon>
@@ .
patch -p0 <<'@@ .'
Index: openpkg-web/security/OpenPKG-SA-2004.019-kolab.txt
============================================================================
$ cvs diff -u -r0 -r1.1 OpenPKG-SA-2004.019-kolab.txt
--- /dev/null 2004-05-05 15:18:56.000000000 +0200
+++ OpenPKG-SA-2004.019-kolab.txt 2004-05-05 15:18:56.000000000 +0200
@@ -0,0 +1,79 @@
+________________________________________________________________________
+
+OpenPKG Security Advisory The OpenPKG Project
+http://www.openpkg.org/security.html http://www.openpkg.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+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] 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 rootpw.
+
+ Please check whether you are affected by running "<prefix>/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) and its dependent packages (see above), if any, too
+ [3][4].
+
+Solution:
+ Select the updated source RPM appropriate for your OpenPKG release
+ [5][5], fetch it from the OpenPKG FTP service [7][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
+ $ <prefix>/bin/openpkg rpm -v --checksig kolab-20040217-2.0.2.src.rpm
+ $ <prefix>/bin/openpkg rpm --rebuild kolab-20040217-2.0.2.src.rpm
+ $ su -
+ # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/kolab-20040217-2.0.2.*.rpm
+
+ Additionally, we recommend that you rebuild and reinstall
+ all dependent packages (see above), if any, too [3][4].
+________________________________________________________________________
+
+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 <[EMAIL PROTECTED]>" (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.
+________________________________________________________________________
+
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
