SUSE Linux Advisories: squid, cvs Jun 10, 2004, 03 :58 UTC (0 Talkback[s]) (1905 reads)
SUSE Security Announcement
Package: squid
Announcement-ID: SuSE-SA:2004:016
Date: Wednesday, Jun 9th 2004 16:30 MEST
Affected products: 8.2, 9.0, 9.1
Vulnerability Type: remote system compromise
Severity (1-10): 5
SUSE default package: no
Cross References: CAN-2004-0541
Content of this advisory:
security vulnerability resolved:
buffer overflow
problem description, discussion, solution and upgrade information
pending vulnerabilities, solutions, workarounds:
icecast
sitecopy
cadaver
tla
OpenOffice_org
tripwire
postgresql
lha
3) standard appendix (further information)
1) problem description, brief discussion, solution, upgrade information
Squid is a feature-rich web-proxy with support for various web-related
protocols.
The NTLM authentication helper application of Squid is vulnerable to
a buffer overflow that can be exploited remotely by using a long
password to execute arbitrary code.
NTLM authentication is enabled by default in the Squid package that
is shipped by SUSE LINUX.
There is no workaround known other then turning off the NTLM
authentication.
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.
2) Pending vulnerabilities in SUSE Distributions and Workarounds:
icecast
The icecast service is vulnerable to a remote denial-of-service
attack. Update packages will be available soon.
sitecopy
The sitecopy package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages will be
available soon.
cadaver
The cadaver package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages will be
available soon.
tla
The tla package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages are
available on our FTP servers.
OpenOffice_org
The OpenOffice_org package includes a vulnerable version
of the neon library (CAN-2004-0179, CAN-2004-0398). Update packages
will be available soon.
tripwire
A format string bug in tripwire can be exploited locally
to gain root permissions. Update packages will be available soon.
postgresql
A buffer overflow in psqlODBC could be exploited to crash the
application using it. E.g. a PHP script that uses ODBC to access a
PostgreSQL database can be utilized to crash the surrounding Apache
web-server. Other parts of PostgreSQL are not affected.
Update packages will be available soon.
lha
Minor security fix for a buffer overflow while handling command
line options. This buffer overflow could be exploited in conjunction
with other mechanisms to gain higher privileges or access the system
remotely.
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:
md5sums as provided in the (cryptographically signed) announcement.
using the internal gpg signatures of the rpm package.
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.
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:
gpg is installed
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:
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: cvs
Announcement-ID: SuSE-SA:2004:015
Date: Wed Jun 9 15:00:00 MEST 2004
Affected products: 8.0, 8.1, 8.2, 9.0, 9.1
SuSE Firewall on CD 2 - VPN
SuSE Firewall on CD 2
SuSE Linux Enterprise Server 7, 8
SuSE Linux Office Server
UnitedLinux 1.0
Vulnerability Type: remote command execution
Severity (1-10): 6
SUSE default package: No.
Cross References: CAN-2004-0416
CAN-2004-0417
CAN-2004-0418
Content of this advisory:
security vulnerability resolved: various security issues in cvs
problem description, discussion, solution and upgrade information
pending vulnerabilities, solutions, workarounds:
icecast
sitecopy
cadaver
tla
OpenOffice_org
tripwire
postgresql
lha
apache/mod_ssl
standard appendix (further information)
1) problem description, brief discussion, solution, upgrade information
The Concurrent Versions System (CVS) offers tools which allow developers
to share and maintain large software projects.
Various remotely exploitable conditions have been found during a
source code review of CVS done by Stefan Esser and Sebastian Krahmer
(SuSE Security-Team).
These bugs allow remote attackers to execute arbitrary code as the user
the CVS server runs as. Since there is no easy workaround we strongly
recommend to update the cvs package.
The update packages fix vulnerabilities which have been assigned the
CAN numbers CAN-2004-0416, CAN-2004-0417 and CAN-2004-0418.
The cvs packages shipped by SUSE (as well as our recent updates for CVS)
are not vulnerable to CAN-2004-0414.
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.
2) Pending vulnerabilities in SUSE Distributions and Workarounds:
icecast
The icecast service is vulnerable to a remote denial-of-service
attack. Update packages will be available soon.
sitecopy
The sitecopy package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages will be
available soon.
cadaver
The cadaver package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages will be
available soon.
tla
The tla package includes a vulnerable version of the
neon library (CAN-2004-0179, CAN-2004-0398). Update packages will be
available soon.
OpenOffice_org
The OpenOffice_org package includes a vulnerable version
of the neon library (CAN-2004-0179, CAN-2004-0398). Update packages
will be available soon.
tripwire
A format string bug in tripwire can be exploited locally
to gain root permissions. Update packages will be available soon.
postgresql
A buffer overflow in psqlODBC could be exploited to crash the
application using it. E.g. a PHP script that uses ODBC to access a
PostgreSQL database can be utilized to crash the surrounding Apache
webserver. Other parts of PostgreSQL are not affected.
Update packages will be available soon.
lha
Minor security fix for a buffer overflow while handling command
line options. This buffer overflow could be exploited in conjunction
with other mechanisms to gain higher privileges or access the system
remotely.
apache/mod_ssl
A buffer overflow in a uuencode function of mod_ssl has been fixed as
well as various minor bugs (CAN-2003-0987, CAN-2003-0020, CAN-2004-0174
and CAN-2003-0993). New packages are available on our ftp servers.
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:
md5sums as provided in the (cryptographically signed) announcement.
using the internal gpg signatures of the rpm package.
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.
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:
gpg is installed
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:
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>
