This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig201F475F4B7EF8EA4DBA6E03
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

---------------------------------------------------------------------
               Fedora Legacy Update Advisory

Synopsis:          Updated libc-client packages fixes security issue
Advisory ID:       FLSA:184098
Issue date:        2006-04-04
Product:           Fedora Core 2
Keywords:          Bugfix, Security
CVE Names:         CVE-2005-2933
---------------------------------------------------------------------


---------------------------------------------------------------------
1. Topic:

Updated libc-client packages that fix a buffer overflow issue are now
available.

C-client is a common API for accessing mailboxes.

2. Relevant releases/architectures:

Fedora Core 2 - i386

3. Problem description:

A buffer overflow flaw was discovered in the way C-client parses user
supplied mailboxes. If an authenticated user requests a specially
crafted mailbox name, it may be possible to execute arbitrary code on a
server that uses C-client to access mailboxes. The Common
Vulnerabilities and Exposures project has assigned the name
CVE-2005-2933 to this issue.

All users of libc-client should upgrade to these updated packages, which
contain a backported patch that resolves this issue.

4. Solution:

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade.  Only those
RPMs which are currently installed will be updated.  Those RPMs which
are not installed but included in the list will not be updated.  Note
that you can also use wildcards (*.rpm) if your current directory *only*
contains the desired RPMs.

Please note that this update is also available via yum and apt.  Many
people find this an easier way to apply updates.  To use yum issue:

yum update

or to use apt:

apt-get update; apt-get upgrade

This will start an interactive process that will result in the
appropriate RPMs being upgraded on your system.  This assumes that you
have yum or apt-get configured for obtaining Fedora Legacy content.
Please visit http://www.fedoralegacy.org/docs for directions on how to
configure yum and apt-get.

5. Bug IDs fixed:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D184098

6. RPMs required:

Fedora Core 2:

SRPM:
http://download.fedoralegacy.org/fedora/2/updates/SRPMS/libc-client-2002e=
-5.1.legacy.src.rpm

i386:
http://download.fedoralegacy.org/fedora/2/updates/i386/libc-client-2002e-=
5.1.legacy.i386.rpm
http://download.fedoralegacy.org/fedora/2/updates/i386/libc-client-devel-=
2002e-5.1.legacy.i386.rpm


7. Verification:

SHA1 sum                                 Package Name
---------------------------------------------------------------------

5232f6a722f64fac4c5e09ca3d34a8e5d33192ed
fedora/2/updates/i386/libc-client-2002e-5.1.legacy.i386.rpm
5e03f3725e30f607708e8da1e9c1537d6e929a29
fedora/2/updates/i386/libc-client-devel-2002e-5.1.legacy.i386.rpm
489cbea579ce3fece1527c68df20f24e8c9bfe75
fedora/2/updates/SRPMS/libc-client-2002e-5.1.legacy.src.rpm

These packages are GPG signed by Fedora Legacy for security.  Our key is
available from http://www.fedoralegacy.org/about/security.php

You can verify each package with the following command:

    rpm --checksig -v <filename>

If you only wish to verify that each package has not been corrupted or
tampered with, examine only the sha1sum with the following command:

    sha1sum <filename>

8. References:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2005-2933

9. Contact:

The Fedora Legacy security contact is <secnotice@fedoralegacy.org>. More
project details at http://www.fedoralegacy.org

---------------------------------------------------------------------



--------------enig201F475F4B7EF8EA4DBA6E03
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iD8DBQFEMxPILMAs/0C4zNoRAtKjAKCqrsFMLuPnsgIQNY9OYdoEPV0luACgjdxj
I9DdI4Z2oozPcUiuYWRjSjA=
=T3Nt
-----END PGP SIGNATURE-----

--------------enig201F475F4B7EF8EA4DBA6E03--