Bugzilla Bug 38256

Form the advisory:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



KDE Security Advisory: VCF file information reader vulnerability
Original Release Date: 2004-01-14
URL: http://www.kde.org/info/security/advisory-20040114-1.txt

0. References


1. Systems affected:

        All versions of kdepim as distributed with KDE versions 3.1.0
        through 3.1.4 inclusive. 


2. Overview:

        The KDE team has found a buffer overflow in the file 
        information reader of VCF files. 

        The Common Vulnerabilities and Exposures project (cve.mitre.org)
        has assigned the name CAN-2003-0988 to this issue.


3. Impact:

        A carefully crafted .VCF file potentially enables local attackers
        to compromise the privacy of a victim's data or execute
        arbitrary commands with the victim's privileges. 

        By default, file information reading is disabled for remote files.
        However, if previews are enabled for remote files, remote
        attackers may be able to compromise the victim's account.


4. Solution:

        As a workaround, remove the kfile_vcf.desktop file.

        Users of KDE 3.1.x are advised to upgrade to KDE 3.1.5. A patch for
        KDE 3.1.4 is available for users who are unable to upgrade to 
        KDE 3.1.5.


5. Patch:

        A patch for KDE 3.1.4 is available from
        ftp://ftp.kde.org/pub/kde/security_patches : 

        26469366cc393e50ff80d6dca8c74c58  post-3.1.4-kdepim-kfile-plugins.diff


6. Time line and credits:

        15/12/2003 KDE developer Dirk Mueller discovers vulnerability.
        15/12/2003 Patches for the vulnerability are applied to CVS and
                   release preparations for KDE 3.1.5 are started.

        14/01/2004 Public advisory.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFABUiwvsXr+iuy1UoRAmf2AKC4JiwDwfDXGME6SZkTF8sVqginEgCgisjC
MLH9/a8f1cFs0iJ2ebdiShM=
=Uoit
-----END PGP SIGNATURE-----

note for security folks/gleppers: this is fixed by an upgrade to kdelibs-3.1.5
(or 3.2.0), which is in portage.

sparc,amd64: could you guys please move either 3.1.5 or 3.2.0 to stable ?

all other archs already have moved to one of those

Sorry, just got back into the swing of things.  Building KDE-3.2.0 now and if
there aren't any problems I'll stabilize it.  Was having problems with
kde-3.1.5 components building but hoping 3.2.0 fixes them.

OK, having trouble building kde because of a dependency and xine-lib's libtool
not doing the right thing.  This is causing kdeaddons to fail consistantly,
which is causing problems stabilizing.  Trying various elibtoolize args in
xine-lib currently, but if anyone has any suggestions to help get this fixed,
that would be great.

The error seems to be related to the fact that kdemultimedia was built before a
recent libtool fix was made to xine-lib.  Re-emerging kdemultimedia now,
hopefully that will make kdeaddons happy.

Rebuilding kdemultimedia fixed the problem.

KDE-3.2.0 is new stable on sparc.

At the time of this announcment was sparc the only arch affected? IE was it
stable already for all other arches? 

we still need amd64 [thats why they're in the cc list still]

3.2.0 is stable on amd64... Going to mark 3.1.5 stable as well today...

GLSA 200404-02 issued. 

Did you CC -core this time?