Mandrake alert: rsync update
Sebastian Krahmer of the SuSE Security Team performed an audit on the rsync tool and discovered that in several places signed and unsigned numbers were mixed, with the end result being insecure code. These flaws could be abused by remote users to write 0 bytes into rsync's memory and trick rsync into executing arbitrary code on the server. It is recommended that all Mandrake Linux users update rsync immediately. As well, rsync server administrators should seriously consider making use of the "use chroot", "read only", and "uid" options as these can significantly reduce the impact that security problems in rsync (or elsewhere) have on the server.
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
Mandrake Linux Security Update Advisory
________________________________________________________________________
Package name: rsync
Advisory ID: MDKSA-2002:009
Date: January 28th, 2002
Affected versions: 7.1, 7.2, 8.0, 8.1, Corporate Server 1.0.1
Single Network Firewall 7.2
________________________________________________________________________
Problem Description:
Sebastian Krahmer of the SuSE Security Team performed an audit on the
rsync tool and discovered that in several places signed and unsigned
numbers were mixed, with the end result being insecure code. These
flaws could be abused by remote users to write 0 bytes into rsync's
memory and trick rsync into executing arbitrary code on the server.
It is recommended that all Mandrake Linux users update rsync
immediately. As well, rsync server administrators should seriously
consider making use of the "use chroot", "read only", and "uid" options
as these can significantly reduce the impact that security problems in
rsync (or elsewhere) have on the server.
________________________________________________________________________
References:
________________________________________________________________________
Updated Packages:
Mandrake Linux 7.1:
24ec7cf554ef39f1c80508e62de83487 7.1/RPMS/rsync-2.4.6-3.2mdk.i586.rpm
09a4383e4edf3ac2a6806d05426ea1da 7.1/SRPMS/rsync-2.4.6-3.2mdk.src.rpm
Mandrake Linux 7.2:
a77115dd3c3325d49926bd7536210e4e 7.2/RPMS/rsync-2.4.6-3.1mdk.i586.rpm
769d981c69c3827765c93ed11040002a 7.2/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
Mandrake Linux 8.0:
df39f2e4b12f8fd4688af4b69f1f7b3f 8.0/RPMS/rsync-2.4.6-3.1mdk.i586.rpm
769d981c69c3827765c93ed11040002a 8.0/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
Mandrake Linux 8.0/ppc:
6ed6ea741a2f9404eaceb4c6fc2eef67 ppc/8.0/RPMS/rsync-2.4.6-3.1mdk.ppc.rpm
769d981c69c3827765c93ed11040002a ppc/8.0/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
Mandrake Linux 8.1:
048f479dbf9be95eb7e1bf59790d0b22 8.1/RPMS/rsync-2.4.6-3.1mdk.i586.rpm
769d981c69c3827765c93ed11040002a 8.1/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
Mandrake Linux 8.1/ia64:
bcb82a2d2df81b692024eeb6dd06b9cf ia64/8.1/RPMS/rsync-2.4.6-3.1mdk.ia64.rpm
769d981c69c3827765c93ed11040002a ia64/8.1/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
Corporate Server 1.0.1:
24ec7cf554ef39f1c80508e62de83487 1.0.1/RPMS/rsync-2.4.6-3.2mdk.i586.rpm
09a4383e4edf3ac2a6806d05426ea1da 1.0.1/SRPMS/rsync-2.4.6-3.2mdk.src.rpm
Single Network Firewall 7.2:
a77115dd3c3325d49926bd7536210e4e snf7.2/RPMS/rsync-2.4.6-3.1mdk.i586.rpm
769d981c69c3827765c93ed11040002a snf7.2/SRPMS/rsync-2.4.6-3.1mdk.src.rpm
________________________________________________________________________
Bug IDs fixed (see https://qa.mandrakesoft.com for more information):
________________________________________________________________________
To upgrade automatically, use MandrakeUpdate. The verification of md5
checksums and GPG signatures is performed automatically for you.
If you want to upgrade manually, download the updated package from one
of our FTP server mirrors and upgrade with "rpm -Fvh *.rpm". A list of
FTP mirrors can be obtained from:
http://www.mandrakesecure.net/en/ftp.php
Please verify the update prior to upgrading to ensure the integrity of
the downloaded package. You can do this with the command:
rpm --checksig <filename>
All packages are signed by MandrakeSoft for security. You can obtain
the GPG public key of the Mandrake Linux Security Team from:
https://www.mandrakesecure.net/RPM-GPG-KEYS
Please be aware that sometimes it takes the mirrors a few hours to
update.
You can view other update advisories for Mandrake Linux at:
http://www.mandrakesecure.net/en/advisories/
MandrakeSoft has several security-related mailing list services that
anyone can subscribe to. Information on these lists can be obtained by
visiting:
http://www.mandrakesecure.net/en/mlist.php
If you want to report vulnerabilities, please contact
security@linux-mandrake.com
________________________________________________________________________
Type Bits/KeyID Date User ID
pub 1024D/22458A98 2000-07-10 Linux Mandrake Security Team
<security@linux-mandrake.com>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
mQGiBDlp594RBAC2tDozI3ZgQsE7XwxurJCJrX0L5vx7SDByR5GHDdWekGhdiday
L4nfUax+SeR9SCoCgTgPW1xB8vtQc8/sinJlMjp9197a2iKM0FOcPlkpa3HcOdt7
WKJqQhlMrHvRcsivzcgqjH44GBBJIT6sygUF8k0lU6YnMHj5MPc/NGWt8wCg9vKo
P0l5QVAFSsHtqcU9W8cc7wMEAJzQsAlnvPXDBfBLEH6u7ptWFdp0GvbSuG2wRaPl
hynHvRiE01ZvwbJZXsPsKm1z7uVoW+NknKLunWKB5axrNXDHxCYJBzY3jTeFjsqx
PFZkIEAQphLTkeXXelAjQ5u9tEshPswEtMvJvUgNiAfbzHfPYmq8D6x5xOw1IySg
2e/LBACxr2UJYCCB2BZ3p508mAB0RpuLGukq+7UWiOizy+kSskIBg2O7sQkVY/Cs
iyGEo4XvXqZFMY39RBdfm2GY+WB/5NFiTOYJRKjfprP6K1YbtsmctsX8dG+foKsD
LLFs7OuVfaydLQYp1iiN6D+LJDSMPM8/LCWzZsgr9EKJ8NXiyrQ6TGludXggTWFu
ZHJha2UgU2VjdXJpdHkgVGVhbSA8c2VjdXJpdHlAbGludXgtbWFuZHJha2UuY29t
PohWBBMRAgAWBQI5aefeBAsKBAMDFQMCAxYCAQIXgAAKCRCaqNDQIkWKmK6LAKCy
/NInDsaMSI+WHwrquwC5PZrcnQCeI+v3gUDsNfQfiKBvQSANu1hdulqIRgQQEQIA
BgUCOtNVGQAKCRBZ5w3um0pAJJWQAKDUoL5He+mKbfrMaTuyU5lmRyJ0fwCgoFAP
WdvQlu/kFjphF740XeOwtOqIRgQQEQIABgUCOu8A6QAKCRBynDnb9lq3CnpjAJ4w
Pk0SEE9U4r40IxWpwLU+wrWVugCdFfSPllPpZRCiaC7HwbFcfExRmPa5AQ0EOWnn
7xAEAOQlTVY4TiNo5V/iP0J1xnqjqlqZsU7yEBKo/gZz6/+hx75RURe1ebiJ9F77
9FQbpJ9Epz1KLSXvq974rnVb813zuGdmgFyk+ryA/rTR2RQ8h+EoNkwmATzRxBXV
Jb57fFQjxOu4eNjZAtfII/YXb0uyXXrdr5dlJ/3eXrcO4p0XAAMFBACCxo6Z269s
+A4v8C6Ui12aarOQcCDlV8cVG9LkyatU3FNTlnasqwo6EkaP572448weJWwN6SCX
Vl+xOYLiK0hL/6Jb/O9Agw75yUVdk+RMM2I4fNEi+y4hmfMh2siBv8yEkEvZjTcl
3TpkTfzYky85tu433wmKaLFOv0WjBFSikohGBBgRAgAGBQI5aefvAAoJEJqo0NAi
RYqYid0AoJgeWzXrEdIClBOSW5Q6FzqJJyaqAKC0Y9YI3UFlE4zSIGjcFlLJEJGX
lA==
=0ahQ
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8VcIqmqjQ0CJFipgRAtQMAJ98nYIh7evTI+Pi5Y/cKnZiwh1lOACeOQmf
W0uVFvnuQAWsaAwGGmTIxNg=
=aMW6
-----END PGP SIGNATURE-----
|
This topic does not have any threads posted yet!
You cannot post until you login.