Simon
The rsync security fix released by RedHat was also broken :-( Many other distributions have yet to release any fixes at all.
Make sure that you don't deploy the broken one from the update CD that I prepared (just) in time for the CLUG/ALUG Cheveley meet! (Best annotate the second 020126 Update CD with a warning)
Here are the details of the new package: rsync-2.4.6-10; the full RHSA security notice is appended. It contains useful hints for running rsync to reduce security risks.
The rsync included on the Update CD was the broken -8 version.
This bugfixed release reached the European FTP mirrors when they synchonized in the early hours of this morning.
--James
-------- Original Message -------- Subject: [RHSA-2002:018-10] New rsync packages available Date: Wed, 30 Jan 2002 16:10 -0500 From: redhat-announce-list-admin@redhat.com Reply-To: redhat-announce-list@redhat.com To: redhat-watch-list@redhat.com CC: bugtraq@securityfocus.com, linux-security@redhat.com
--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory
Synopsis: New rsync packages available Advisory ID: RHSA-2002:018-10 Issue date: 2002-01-23 Updated on: 2002-01-30 Product: Red Hat Linux Keywords: rsync signed unsigned daemon Cross references: Obsoletes: ---------------------------------------------------------------------
1. Topic:
New rsync packages are available; these fix a remotely exploitable problem in the I/O functions. These include the security patch from the recently released rsync-2.5.2. It is strongly recommended that all users of rsync upgrade to the fixed packages.
2002-01-28: There was an error in the original bugfix patch for the security problem - the new rsync could fail under some circumstances. This has been fixed in a new build.
2. Relevant releases/architectures:
Red Hat Linux 6.2 - alpha, i386, sparc
Red Hat Linux 7.0 - alpha, i386
Red Hat Linux 7.1 - alpha, i386, ia64
Red Hat Linux 7.2 - i386, ia64
3. Problem description:
rsync is a powerful tool used for mirroring directory structures across machines. rsync has been found to contain several signed/unsigned bugs in its I/O functions which are remotely exploitable. A remote user can crash the rsync server/client and execute code as the user running the rsync server or client.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2002-0048 to this issue.
All users of rsync should upgrade their packages. In addition rsync server administrators should consider using the "use chroot", "uid", and "read only" options, which can significantly reduce the impact of a security problem in rsync or elsewhere.
Thanks go to Sebastian Krahmer for providing a patch for this vulnerability and to Andrew Tridgell and Martin Pool for their rapid response.
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. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):
58874 - New rsync package corrupts files during transfer. 58878 - rsync segfaults
6. RPMs required:
Red Hat Linux 6.2:
SRPMS: ftp://updates.redhat.com/6.2/en/os/SRPMS/rsync-2.4.6-1.6.src.rpm
alpha: ftp://updates.redhat.com/6.2/en/os/alpha/rsync-2.4.6-1.6.alpha.rpm
i386: ftp://updates.redhat.com/6.2/en/os/i386/rsync-2.4.6-1.6.i386.rpm
sparc: ftp://updates.redhat.com/6.2/en/os/sparc/rsync-2.4.6-1.6.sparc.rpm
Red Hat Linux 7.0:
SRPMS: ftp://updates.redhat.com/7.0/en/os/SRPMS/rsync-2.4.6-10.src.rpm
alpha: ftp://updates.redhat.com/7.0/en/os/alpha/rsync-2.4.6-10.alpha.rpm
i386: ftp://updates.redhat.com/7.0/en/os/i386/rsync-2.4.6-10.i386.rpm
Red Hat Linux 7.1:
SRPMS: ftp://updates.redhat.com/7.1/en/os/SRPMS/rsync-2.4.6-10.src.rpm
alpha: ftp://updates.redhat.com/7.1/en/os/alpha/rsync-2.4.6-10.alpha.rpm
i386: ftp://updates.redhat.com/7.1/en/os/i386/rsync-2.4.6-10.i386.rpm
ia64: ftp://updates.redhat.com/7.1/en/os/ia64/rsync-2.4.6-10.ia64.rpm
Red Hat Linux 7.2:
SRPMS: ftp://updates.redhat.com/7.2/en/os/SRPMS/rsync-2.4.6-10.src.rpm
i386: ftp://updates.redhat.com/7.2/en/os/i386/rsync-2.4.6-10.i386.rpm
ia64: ftp://updates.redhat.com/7.2/en/os/ia64/rsync-2.4.6-10.ia64.rpm
7. Verification:
MD5 sum Package Name -------------------------------------------------------------------------- 3b33976775af0d04ce639915e5c7cb63 6.2/en/os/SRPMS/rsync-2.4.6-1.6.src.rpm 418e264b0ba45fb9d16deff259e462c4 6.2/en/os/alpha/rsync-2.4.6-1.6.alpha.rpm 441409bda25e79567d4a587994b84d76 6.2/en/os/i386/rsync-2.4.6-1.6.i386.rpm 35abb7066b5e5b7092465c33dd24085d 6.2/en/os/sparc/rsync-2.4.6-1.6.sparc.rpm ec10c0deb84328cc553449f4330f1cfd 7.0/en/os/SRPMS/rsync-2.4.6-10.src.rpm b756d3ddf8b2d34d5fe7c6b1a4c1d043 7.0/en/os/alpha/rsync-2.4.6-10.alpha.rpm 2e37e09c1f55d4d825e748a4a2005698 7.0/en/os/i386/rsync-2.4.6-10.i386.rpm ec10c0deb84328cc553449f4330f1cfd 7.1/en/os/SRPMS/rsync-2.4.6-10.src.rpm b756d3ddf8b2d34d5fe7c6b1a4c1d043 7.1/en/os/alpha/rsync-2.4.6-10.alpha.rpm 2e37e09c1f55d4d825e748a4a2005698 7.1/en/os/i386/rsync-2.4.6-10.i386.rpm 7895ca8e94476fe4868c07dad2f079ae 7.1/en/os/ia64/rsync-2.4.6-10.ia64.rpm ec10c0deb84328cc553449f4330f1cfd 7.2/en/os/SRPMS/rsync-2.4.6-10.src.rpm 2e37e09c1f55d4d825e748a4a2005698 7.2/en/os/i386/rsync-2.4.6-10.i386.rpm 7895ca8e94476fe4868c07dad2f079ae 7.2/en/os/ia64/rsync-2.4.6-10.ia64.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: rpm --checksig <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: rpm --checksig --nogpg <filename>
8. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0048
Copyright(c) 2000, 2001, 2002 Red Hat, Inc.
_______________________________________________ Redhat-watch-list mailing list To unsubscribe, visit: https://listman.redhat.com/mailman/listinfo/redhat-watch-list
_______________________________________________ redhat-announce-list mailing list redhat-announce-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-announce-list
On Thu, Jan 31, 2002 at 12:18:41PM +0000, James wrote:
Simon
The rsync security fix released by RedHat was also broken :-( Many other distributions have yet to release any fixes at all.
[Snip]
Anyone that wants to hear about security fixes is surely on all/most of the major security mailing lists? Nice to be concerned for other peoples system welfare but I hate getting one copy of the mail directly and another forwarded on yet another mailing list, *sigh*. Thats 5 times I have seen this email appear, 6 including the direct email from RedHat's security list itself.
Just my $0.02
-------- Original Message -------- Subject: Re: [Alug] (RedHat) rsync-2.4.6-8 Update BROKEN Date: Fri, 1 Feb 2002 09:57:47 +0000 From: James Ray jamesr@pethippo.co.uk To: James jtl1listmail@bigfoot.com CC: ALUG main@lists.alug.org.uk
James Ray wrote:
On Thu, Jan 31, 2002 at 12:18:41PM +0000, James wrote:
Simon
The rsync security fix released by RedHat was also broken :-( Many other distributions have yet to release any fixes at all.
[Snip]
Anyone that wants to hear about security fixes is surely on all/most of the major security mailing lists? Nice to be concerned for other peoples system welfare but I hate getting one copy of the mail directly and another forwarded on yet another mailing list, *sigh*. Thats 5 times I have seen this email appear, 6 including the direct email from RedHat's security list itself.
Just my $0.02
Too Bad that I've added to your information overload sunshine; I just knew that someone would complain. As far as security is concerned, there is one maxim you may also know from assembler programming: Assume Nothing.
I handed out a CD containing updates with this broken rsync on it at an ALUG meeting, so in this instance I had a responsibility to warn the recipient, and anyone else that might had taken copies of it. Some people receive the security notices separately, but get too busy to read 'em. Also - Redhat's listserver often gets constipated and doesn't send out notices in a timely manner.
--James
On Fri, 1 Feb 2002, James wrote:
Too Bad that I've added to your information overload sunshine; I just knew that someone would complain. As far as security is concerned, there is one maxim you may also know from assembler programming: Assume Nothing.
And there is one maxim you may know from netiquette: read the lists for a while before contributing. You will see a big discussion of security posts not long ago.
I handed out a CD containing updates with this broken rsync on it at an ALUG meeting, so in this instance I had a responsibility to warn the recipient, and anyone else that might had taken copies of it.
"Hi, I recently distributed CDs with this flaw <url>, anyone that got one should check their systems" would have been more appropriate.
Also - Redhat's listserver often gets constipated and doesn't send out notices in a timely manner.
So use a proper distro :-)
Don't get me wrong, I'm not trying to be unfriendly, but James Ray is absolutely right (although I hate admitting it!) when he says "don't post security announcements here" although his justifications may be a little off. See the ALUG archives for details of why security posts are a Bad Thing.
Andrew.
-
Andrew Savory -
James -
James Ray