SUSE Linux Advisories: cups, apache2

Sep 16, 2004, 15:14 (0 Talkback[s])

SUSE Security Announcement

Package: cups
Announcement-ID: SUSE-SA:2004:031
Date: Wednesday, Sep 15th, 15:30:00 MEST 2004
Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Enterprise Server 8, 9 SUSE Linux Desktop 1.0
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE default package: Yes.
Cross References: CAN-2004-0801 CAN-2004-0558

Content of this advisory:

security vulnerability resolved:
- remote command execution and remote DoS in CUPS problem description
solution/workaround
special instructions and notes
package location and checksums
pending vulnerabilities, solutions, workarounds:
- squid
- OpenOffice
- mozilla
- mpg123
- ImageMagick
standard appendix (further information)

1) problem description, brief discussion

The Common Unix Printing System (CUPS) enables local and remote users to obtain printing functionallity via the Internet Printing Protocol (IPP). Alvaro Martinez Echevarria has found a remote Denial of Service condition within CUPS which allows remote users to make the cups server unresponsive. Additionally the SUSE Security Team has discovered a flaw in the foomatic-rip print filter which is commonly installed along with cups. It allows remote attackers, which are listed in the printing ACLs, to execute arbitrary commands as the printing user 'lp'.

2) solution/workaround

If you use CUPS, we recommend an update in any case. Additionally the IPP port (TCP port 631) should be firewalled and the printing ACLs should be set up in a way to reflect the local security policy.

3) special instructions and notes

After successfully updating the cups package, you need to run the following command as root:

rccups restart

4) package location and checksums

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.
Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web.

x86 Platform:

SUSE Linux 8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-1.1.18-96.i586.rpm 5092cfbf2d9f71b53cfa571d23ac8e26
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-libs-1.1.18-96.i586.rpm 1b52320ac8e50797b9e140ba0339008c
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-client-1.1.18-96.i586.rpm b0cc87346a3b2270081123bbb5fd932a
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-1.1.18-96.i586.patch.rpm d67014a864afaa86952ed752d89a251a
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-libs-1.1.18-96.i586.patch.rpm be6ae574c2f26a7f07d1b5e16f4ede02
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/cups-client-1.1.18-96.i586.patch.rpm c176435d584a763ae5b57dcde996f82c
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/cups-1.1.18-96.src.rpm 870f0825115fdf9526beb6e1ec867381

SUSE Linux 8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-1.1.15-170.i586.rpm b8a1daf19c2fa58fecc3f9dafb8c4c8d
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-libs-1.1.15-170.i586.rpm 9f7a2dbc92804cb54749e72426d79a62
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-client-1.1.15-170.i586.rpm 7a82aedac6586fa27109e3576f5c4c27
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-1.1.15-170.i586.patch.rpm 341ebcf57e793a836b5475353cb21e7c
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-libs-1.1.15-170.i586.patch.rpm 3b75cf2265150044560555785e8e4c82
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cups-client-1.1.15-170.i586.patch.rpm 926eca878ee8c36c4efa509d7b7243d4
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/cups-1.1.15-170.src.rpm ffc7b24d6638f04933621b9b49bb9e9e

x86-64 Platform:

5) Pending vulnerabilities in SUSE Distributions and Workarounds:

squid
The NTLM authentication in squid suffers from a DoS vulnerability. New packages are currently being tested and will soon be available on our ftp servers.
OpenOffice
OpenOffice sets the permissions of tmp-files according to the umask, which might be unsuitable. This will be fixed in upcoming distributions. If you work in an untrusted environment, you may set the $TEMP, $TMP and $TMPDIR environment variables to a location within your $HOME as a workaround.
mozilla
We are in the process of releasing updates for mozilla (and related browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718, CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004-0760, CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and CAN-2004-0765. We will give you concrete details in a separate mozilla advisory when the updates are available.
mpg123
A buffer overflow in the decoding of data streams has been fixed. New packages are available on our ftp servers. CAN-2004-0805 has been assigned to this issue.
ImageMagick
A buffer overflow in the code handling BMP images has been fixed. New packages are available on our ftp servers. CAN-2004-0827 has been assigned to this issue.

6) 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.
3. 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 security@suse.de), 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.
4. 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 un-installed rpm package file. Prerequisites:
  1. gpg is installed
  2. 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 "build@suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level 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:
suse-security@suse.com
general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to
<suse-security-subscribe@suse.com>.

suse-security-announce@suse.com
SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.

For general information or the frequently asked questions (faq) send mail to:

<suse-security-info@suse.com> or <suse-security-faq@suse.com> respectively.

SUSE's security contact is <security@suse.com> or <security@suse.de>. The <security@suse.de> 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 clear-text signature shows proof of the authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>

SUSE Security Announcement

Package: apache2
Announcement-ID: SUSE-SA:2004:032
Date: Wednesday, Sep 15th 2004 16:00 MEST
Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Enterprise Server 9
Vulnerability Type: remote denial-of-service
Severity (1-10): 5
SUSE default package: no
Cross References: CAN-2004-0747 CAN-2004-0786

Content of this advisory:

security vulnerability resolved:
- remote denial-of-service
- local buffer overflow problem description
solution/workaround
special instructions and notes
package location and checksums
pending vulnerabilities, solutions, workarounds:
- samba
- a2ps
- mozilla
- mc
- squid
- gtk2
- gaim
- nessus
standard appendix (further information)

1) problem description, brief discussion

The Apache daemon is running on most of the web-servers used in the Internet today.
The Red Hat ASF Security-Team and the Swedish IT Incident Center within the National Post and Telecom Agency (SITIC) have found a bug in apache2 each.
The first vulnerability appears in the apr_uri_parse() function while handling IPv6 addresses. The affected code passes a negative length argument to the memcpy() function. On BSD systems this can lead to remote command execution due to the nature of the memcpy() implementation. On Linux this bug will result in a remote denial-of-service condition. The second bug is a local buffer overflow that occurs while expanding ${ENVVAR} in the .htaccess and httpd.conf file. Both files are not writeable by normal user by default.

2) solution/workaround

There is no known workaround.

3) special instructions and notes

After the new apache2 packages have been installed you have to restart the apache2 daemon by executing the following command as root: /usr/sbin/rcapache2 restart

4) package location and checksums

x86 Platform:

x86-64 Platform:

5) Pending vulnerabilities in SUSE Distributions and Workarounds:

samba
This version fixes several bugs in the Samba suite including two denial-of-service (DoS) Vulnerabilities. Microsoft Windows XP clients with installed Service Pack 2 crash the Samba (smbd) process while printing. Using macros in the smb.conf 'log file' statement might lead to an infinite recursion. A wrong counter and pointer handling in samba-vscan leads to a crash of the Samba (smbd) process sometimes. A DoS bug in smbd may allow an unauthenticated user to cause smbd to spawn new processes, each one entering an infinite loop. After sending a sufficient amount of packets it is possible to exhaust the memory resources on the server. This issue is known as CAN-2004-0807. A DoS bug in nmbd may allow an attacker to remotely crash the nmbd daemon. This issue is known as CAN-2004-0808. New packages are available on our FTP servers.
a2ps
This update fixes the handling of filenames that include shell metacharacters. Without this patch it was possible to execute shell commands via a2ps by providing a filename that includes metacharacters as an argument. New packages are available on our FTP servers.
mozilla
We are in the process of releasing updates for mozilla (and related browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718, CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004- 0760, CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and CAN-2004-0765. We will give you concrete details in a separate mozilla advisory when the updates are available.
mc
The console filesystem browser mc was found vulnerable to various meta-char attacks in the extfs perl and shell scripts. These bugs can be exploited by providing a malformed archive file to a victim user to execute shell commands with her/his privileges. (CAN-2004-0494) New packages will be available soon.
squid
Certain malformed NTLMSSP packets can crash the NTLM helpers provided by Squid (CAN-2004-0832). New packages will be available soon.
gtk2
This update fixes three vulnerabilities found in the XPM loader code of the GTK Library. They are registered as:
+ CAN-2004-0782 Heap-based overflow in pixbuf_create_from_xpm
+ CAN-2004-0783 Stack-based overflow in xpm_extract_color
+ CAN-2004-0788 icon loader integer overflow.
New packages will be available soon.
gaim
This security update fixes four security issues which are registered as:
+ CAN-2004-0754
An integer overflow in the groupware message handler exists in Gaim.
+ CAN-2004-0784
A shell escape vulnerability in the handling of smiley theme tarball filenames could lead to arbitrary command execution.
+ CAN-2004-0785
Buffer overflows in Gaim could lead to a denial of service or arbitrary code execution.
Additionally a buffer overflow in the URL parsing code of gaim is fixed. This bug let to remote system compromise with the privileges of the user running gaim.
nessus
The nessus-adduser creates temporary files in $TMPDIR in an insecure manner. New packages will be available soon.

6) 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.
3. 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 security@suse.de), 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.
4. 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 un-installed rpm package file. Prerequisites:
  1. gpg is installed
  2. 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 "build@suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level 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:
suse-security@suse.com
general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to
<suse-security-subscribe@suse.com>.

suse-security-announce@suse.com
SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.

For general information or the frequently asked questions (faq) send mail to:

<suse-security-info@suse.com> or
<suse-security-faq@suse.com> respectively.

SUSE's security contact is <security@suse.com> or <security@suse.de>.
The <security@suse.de> public key is listed below.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>

Top White Papers

Subscribe to Our Daily Newsletter

Current Newswire:

More on LinuxToday

SUSE Linux Advisories: cups, apache2