Home > Security > Advisories

Advisories

Mandriva Advisories

Package name cups
Date February 5th, 2001
Advisory ID MDKSA-2001:020-1
Affected versions 7.2
Synopsis Updated cups packages fix upgrade difficulties

Problem Description

A problem exists in all versions of CUPS prior to 1.1.5 with the
httpGets() function. It could go into an infinite loop if a line
longer than the input buffer size was sent by a client. This could be
used as a DoS attack. As well, all occurances of sprintf() calls were
changed to snprintf(), and all occurances of strcpy() calls were
changed to strncpy() calls, both of which protect against buffer
overflows. Finally, CUPS now defaults to not broadcasting the printer
information anymore by default, and by default access is only allowed
from the local machine.

Update:

The previously released packages were improperly constructed using the
new library method currently used in the Linux-Mandrake Cooker, and as
such caused upgrade problems for existing 7.2 users. This update
corrects this and does not use the libcups1(-devel) packages which
caused the problem. Users who have already upgraded to the updated
cups packages announced last week will need to uninstall the libcups1
packages and then upgrade cups again. To do this, at the command line
execute the following commands prior to running MandrakeUpdate:

rpm -e libcups1-devel
rpm -e libcups1 --nodeps

Now you can update the cups packages properly via MandrakeUpdate.

Updated Packages

Mandrakelinux 7.2

 41bdfcc888ad32677955b31cbb1d730e  7.2/RPMS/cups-1.1.6-3.1mdk.i586.rpm
29f054e667705f42d415cebb3cf4b4ab  7.2/RPMS/cups-common-1.1.6-3.1mdk.i586.rpm
d4c1d7f521d4a0029a48f7eb829b3334  7.2/RPMS/cups-devel-1.1.6-3.1mdk.i586.rpm
ad278aa654b3607a77c22c2fd2583fb4  7.2/SRPMS/cups-1.1.6-3.1mdk.src.rpm

Upgrade

To upgrade automatically, use MandrivaUpdate.


Verification

Please verify the update prior to upgrading to ensure the integrity of the downloaded package. You can do this with the command :

                rpm --checksig package.rpm
                

You can get the GPG public key of the Mandriva Security Team to verify the GPG signature of each RPM.

If you use MandrivaUpdate, the verification of md5 checksum and GPG signature is performed automatically for you.