Published: 2002-01-25 17:18:39
Updated: 2002-01-25 17:18:39
______________________________________________________________________________ SuSE Security Announcement Package: rsync Announcement-ID: SuSE-SA:2002:004 Date: Fri Jan 25 17:00:00 CET 2002 Affected SuSE versions: 6.4, 7.0, 7.1, 7.2, 7.3 Vulnerability Type: remote command executionn Severity (1-10): 7 SuSE default package: no Other affected systems: All systems with vulnerable rsync. Content of this advisory: 1) security vulnerability resolved: rsync negative array indexing problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The rsync program allows users and administrators to synchronize files and whole directory structures on different machines. It is common practise to allow remote users to mirror ftp servers via anonymous rsync access. There exist several signedness bugs within the rsync program which allow remote attackers to write 0-bytes to almost arbitrary stack-locations, therefore being able to control the programflow and obtaining a shell remotely. These bugs have been fixed. It is recommended (also stated in the rsync documentation) to use the "use chroot" option in rsyncd's configuration file (/etc/rsyncd.conf) to limit the impact of a possible attack. Since this workaround does not completely solve the security problem, we recommend to update the package as described below. We want to express our gratitude to Andrew Tridgell and Martin Pool, the rsync authors and maintainers, for their excellent cooperation in this matter. Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. To be sure that the update takes effect, kill any existing instances of the rsync-program. In case you run rsync via the inetd superserver, you do not need to restart any of your services. Inetd will automatically use the new binary. If you used run your rsync-service with the "rsync --daemon" command, restart your rsync with "rync --daemon" again, this time using the new binary. i386 Intel Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/rsync-2.4.6-288.i386.rpm ce6d9226a8a9a5644ece29926c1f51d7 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/rsync-2.4.6-288.src.rpm 0e354408f232b25fe0089b97073009a3 SuSE-7.2 ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/rsync-2.4.6-289.i386.rpm 1ff42b8149e21644d23fe71c40a3ec5a source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/rsync-2.4.6-289.src.rpm 83407b4dfad94d21af60ba3e8025e6cd SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/rsync-2.4.6-288.i386.rpm 26533f97af4474b450ad43a171c5571f source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/rsync-2.4.6-288.src.rpm dcd1345446871320962e91d979ddb25b SuSE-7.0 ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/rsync-2.3.2-124.i386.rpm f16f81e5a0a11ba951b6f923cbae2abd source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/rsync-2.3.2-124.src.rpm cd36ce735b4ca91f92fc2f3c7603037f SuSE-6.4 ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/rsync-2.3.2-123.i386.rpm c9330c9123757f89ed94382874122c82 source rpm: ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/rsync-2.3.2-123.src.rpm d97478d6fe9f2419b8700c52be4d888a Sparc Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/rsync-2.4.6-135.sparc.rpm 669f52233aed0766dd72788741691558 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/rsync-2.4.6-135.src.rpm 85ddaa9518d19f6341a68ce254668f0b SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/rsync-2.4.6-135.sparc.rpm d68ebcdba8caa16360e225fc9d28dc54 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/rsync-2.4.6-135.src.rpm b9f1f43d0248b763aef46bd610233285 SuSE-7.0 ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/rsync-2.3.2-5.sparc.rpm 50b9cefa5f4bf86fc1e20184c15fb542 source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/rsync-2.3.2-5.src.rpm ffbc3ff43c339cbbe12317bb98587df3 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/rsync-2.4.6-123.alpha.rpm 3b602bd23179a7b6ce162d2d377394af source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/rsync-2.4.6-123.src.rpm 65f9d53cb48b8456466a27d9cde04339 SuSE-7.0 ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/rsync-2.3.2-30.alpha.rpm 2056422feb3b2b53285413ca746f2f4e source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/rsync-2.3.2-30.src.rpm 88c3a630df0e3073a8be55b0008371a0 SuSE-6.4 ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/rsync-2.3.2-31.alpha.rpm 18ea59b5c4d4641b62cef9c11f535ae8 source rpm: ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/rsync-2.3.2-31.src.rpm 091659d90d3e079c0f8d4518c2c42f9f Power PC Platform: SuSE-7.3 ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/rsync-2.4.6-150.ppc.rpm f5576fca06f5d22b1410aaba399e0791 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/rsync-2.4.6-150.src.rpm 1baeeffafe1c7dd75189cbfe704bddf0 SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/rsync-2.4.6-151.ppc.rpm 04102efb5a83b5190fe6b02146ec522b source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/rsync-2.4.6-151.src.rpm 4a21e9f5b36f6767436c6ea92f5d17e7 SuSE-7.0 ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/rsync-2.3.2-133.ppc.rpm 897e0010ccf09c85a8c8797dc77394e1 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/rsync-2.3.2-133.src.rpm 7ff150ba5f39ab527aa67308154273e2 SuSE-6.4 ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/rsync-2.3.2-133.ppc.rpm 65ac31f12bacb9284fd2286aec7beab0 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/rsync-2.3.2-133.src.rpm 4b43552a939f080a3e93fe65a88bd139 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - pine The popular mail client "pine" was found vulnerable to an attack where shell metacharacters inside an URL could be used to execute arbitrary commands if pine passes the URL to an external viewer on the commandline. The pine packages on SuSE products are not vulnerable to this weakness because they contain a patch that works around this problem since it is not new. - xchat We are working on updates for the xchat packages in the SuSE Linux 7.0 and 7.1 distributions that are vulnerable to an encoding bug while receiving and decoding ctcp datagrams. This bug can lead an xchat IRC client to execute IRC protocol specific commands to an IRC server such as channel mode changes. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key email@example.com), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "firstname.lastname@example.org" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: email@example.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <firstname.lastname@example.org>. email@example.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <firstname.lastname@example.org>. For general information or the frequently asked questions (faq) send mail to: <email@example.com> or <firstname.lastname@example.org> respectively. ===================================================================== SuSE's security contact is <email@example.com> or <firstname.lastname@example.org>. The <email@example.com> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory.