Date: Tue, 7 Jan 2003 04:13 -0500
From: [email protected]
To: [email protected], [email protected]Subject: [RHSA-2002:283-09] Updated cyrus-sasl packages fix buffer overflows
---------------------------------------------------------------------
Red Hat, Inc. Red Hat Security Advisory
Synopsis: Updated cyrus-sasl packages fix buffer overflows
Advisory ID: RHSA-2002:283-09
Issue date: 2003-01-07
Updated on: 2003-01-06
Product: Red Hat Linux
Ключевые слова:, , , , , , , , , cyrus-sasl, buffer, overflow, flaw:buf, (найти похожие документы)
Cross references:=20=20
Obsoletes: RHSA-2001:150
CVE Names: CAN-2002-1347
---------------------------------------------------------------------
1. Topic:
Updated cyrus-sasl packages are now available for Red Hat Linux 8.0. These
packages close buffer overflows present in Cyrus SASL 2.1 and later.
2. Relevant releases/architectures:
Red Hat Linux 8.0 - i386
3. Problem description:
Cyrus SASL is an implementation of the Simple Authentication and Security
Layer, a method for adding authentication support to connection-based
protocols. Cyrus SASL versions 2 prior to 2.1.10 include a number of
buffer overflow vulnerabilities:
Insufficient buffer length checking in user name canonicalization. This
issue would be hard to exploit, but would allow a remote user to execute
arbitrary code on the system.
When performing authentication using LDAP, saslauthd does not allocate
enough memory when it needs to escape special characters in the username
and realm. This issue may be easy to remotely exploit.
The Log writer might not have allocated memory for the trailing \0 in a
message. This issue is probably hard to exploit, although it is possible to
affect the logging data with at least anonymous authentication.
All users of Cyrus-SASL on Red Hat Linux 8.0 are advised to upgrade to the
erratum packages containing Cyrus SASL version 2.1.10 which is not affected
by these vulnerabilities. Other Red Hat Linux releases are not affected by
this vulnerability as they included Cyrus-SASL version 1.5.x.
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 Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
5. RPMs required:
Red Hat Linux 8.0:
SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/cyrus-sasl-2.1.10-1.src.rpm
i386:
ftp://updates.redhat.com/8.0/en/os/i386/cyrus-sasl-2.1.10-1.i386.rpmftp://updates.redhat.com/8.0/en/os/i386/cyrus-sasl-devel-2.1.10-1.i386.rpmftp://updates.redhat.com/8.0/en/os/i386/cyrus-sasl-gssapi-2.1.10-1.i386.rpmftp://updates.redhat.com/8.0/en/os/i386/cyrus-sasl-md5-2.1.10-1.i386.rpmftp://updates.redhat.com/8.0/en/os/i386/cyrus-sasl-plain-2.1.10-1.i386.rpm
6. Verification:
MD5 sum Package Name
--------------------------------------------------------------------------
e291b7bd71cd69825077aba5a3341764 8.0/en/os/SRPMS/cyrus-sasl-2.1.10-1.src.rpm
0bf0d5b2e17a26e06f1b9e2cd02fdae3 8.0/en/os/i386/cyrus-sasl-2.1.10-1.i386.rpm
80d77339fc5a06bed5073cd34019d9f4 8.0/en/os/i386/cyrus-sasl-devel-2.1.10-1.i=
386.rpm
877a229ffe46aa7be012f8d69fa1d544 8.0/en/os/i386/cyrus-sasl-gssapi-2.1.10-1.=
i386.rpm
8568b99569bceb11d237fd302d372113 8.0/en/os/i386/cyrus-sasl-md5-2.1.10-1.i38=
6.rpm
bc69bfc361c0c75c15be0d7557133633 8.0/en/os/i386/cyrus-sasl-plain-2.1.10-1.i=
386.rpm
These packages are GPG signed by Red Hat, Inc. for security. Our key
is available at http://www.redhat.com/about/contact/pgpkey.html
You can verify each package with the following command:
=20=20=20=20
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
=20=20=20=20
md5sum <filename>
7. References:
http://marc.theaimsgroup.com/?l=3Dcyrus-sasl&m=3D103945455024946http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCAN-2002-1347
8. Contact:
The Red Hat security contact is <[email protected]>. More contact
details at http://www.redhat.com/solutions/security/news/contact.html
Copyright(c) 2000, 2001, 2002 Red Hat, Inc.
