Package : clamav
Vulnerability : various DOS vulnerabilities
Problem type : remote DOS
Debian-specific: no
CVE Id(s) : CAN-2005-1922, CAN-2005-1923, CAN-2005-2056, CAN-2005-2070
A number of potential remote DOS vulnerabilities have been identified in
ClamAV. In addition to the four issues identified by CVE ID above, there
are fixes for issues in libclamav/cvd.c and libclamav/message.c.
Together, these issues could allow a carefully crafted message to crash
a ClamAV scanner or exhaust various resources on the machine running the
scanner.
For the stable distribution (sarge), these problems have been fixed in
version 0.84-2.sarge.1.
We recommend that you upgrade your clamav package.
Upgrade instructions
wget url
will fetch the file for you
dpkg -i file.deb
will install the referenced file.
If you are using the apt-get package manager, use the line for
sources.list as given below:
apt-get update
will update the internal database
apt-get upgrade
will install corrected packages
You may use an automated update by adding the resources from the
footer to the proper configuration.
Debian 3.1 (sarge)
Sarge was released for alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390 and sparc.
Package : razor
Vulnerability : email header parsing error
Problem type : remote DOS
Debian-specific: no
CVE Id(s) : CAN-2005-2024
A vulnerability was discovered in the way that Razor parses certain
email headers that could potentially be used to crash the Razor program,
causing a denial of service (DOS).
For the stable distribution (sarge), this problem has been fixed in
version 2.670-1sarge2.
The old stable distribution (woody) is not affected by this issue.
We recommend that you upgrade your razor package.
Upgrade instructions
wget url
will fetch the file for you
dpkg -i file.deb
will install the referenced file.
If you are using the apt-get package manager, use the line for
sources.list as given below:
apt-get update
will update the internal database
apt-get upgrade
will install corrected packages
You may use an automated update by adding the resources from the
footer to the proper configuration.
Debian 3.1 (sarge)
sarge was released for alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390 and sparc.
Stefan Esser discovered an input validation flaw within Trac, a wiki
and issue tracking system, that allows download/upload of files and
therefore can lead to remote code execution in some configurations.
The old stable distribution (woody) does not contain the trac package.
For the stable distribution (sarge) this problem has been fixed in
version 0.8.1-3sarge2.
For the unstable distribution (sid) this problem has been fixed in
version 0.8.4-1.
We recommend that you upgrade your trac package.
Upgrade Instructions
wget url
will fetch the file for you
dpkg -i file.deb
will install the referenced file.
If you are using the apt-get package manager, use the line for
sources.list as given below:
apt-get update
will update the internal database
apt-get upgrade
will install corrected packages
You may use an automated update by adding the resources from the
footer to the proper configuration.
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.
Copyright 2005 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
Red Hat Linux
Red Hat Security Advisory
Synopsis: Important: zlib security update
Advisory ID: RHSA-2005:569-01
Advisory URL: https://rhn.redhat.com/errata/RHSA-2005-569.html
Issue date: 2005-07-06
Updated on: 2005-07-06
Product: Red Hat Enterprise Linux
CVE Names: CAN-2005-2096
1) Summary:
Updated Zlib packages that fix a buffer overflow are now available for Red
Hat Enterprise Linux 4.
This update has been rated as having important security impact by the Red
Hat Security Response Team.
2. Relevant releases/architectures:
Red Hat Enterprise Linux AS version 4 - i386, ia64, ppc, s390, s390x, x86_64
Red Hat Enterprise Linux Desktop version 4 - i386, x86_64
Red Hat Enterprise Linux ES version 4 - i386, ia64, x86_64
Red Hat Enterprise Linux WS version 4 - i386, ia64, x86_64
3. Problem description:
Zlib is a general-purpose lossless data compression library which is used
by many different programs.
Tavis Ormandy discovered a buffer overflow affecting Zlib version 1.2 and
above. An attacker could create a carefully crafted compressed stream that
would cause an application to crash if the stream is opened by a user. As
an example, an attacker could create a malicious PNG image file which would
cause a web browser or mail viewer to crash if the image is viewed. The
Common Vulnerabilities and Exposures project assigned the name
CAN-2005-2096 to this issue.
Please note that the versions of Zlib as shipped with Red Hat Enterprise
Linux 2.1 and 3 are not vulnerable to this issue.
All users should update to these erratum packages which contain a patch
from Mark Adler which corrects this issue.
4. Solution:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
This update is available via Red Hat Network. 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.
Package: zlib
Announcement ID: SUSE-SA:2005:039
Date: Wed, 06 Jul 2005 14:00:00 +0000
Affected Products: 9.1, 9.2, 9.3
SUSE Linux Enterprise Server 9
Novell Linux Desktop 9
Open Enterprise Server
Vulnerability Type: remote denial of service
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CAN-2005-2096
Content of This Advisory:
Security Vulnerability Resolved:
zlib denial of service attack
Problem Description
Solution or Work-Around
Special Instructions and Notes
Package Location and Checksums
Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
Authenticity Verification and Additional Information
1) Problem Description and Brief Discussion
A denial of service condition was fixed in the zlib library.
Any program using zlib to decompress data can be crashed by a specially
handcrafted invalid data stream. This includes web browsers or email
programs able to view PNG images (which are compressed by zlib),
allowing remote attackers to crash browser sessions or potentially
anti virus programs using this vulnerability.
This issue is tracked by the Mitre CVE ID CAN-2005-2096.
Since only zlib 1.2.x is affected, older SUSE products are not affected
by this problem.
2) Solution or Work-Around
Install the updated packages.
3) Special Instructions and Notes
Please restart running programs using zlib.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command
rpm -Fhv <file.rpm>
to apply the update, replacing <file.rpm> with the filename of the
downloaded RPM package.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
Announcement authenticity verification:
SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.
To verify the signature of the announcement, save it as text into a file
and run the command
gpg --verify <file>
replacing <file> with the name of the file where you saved the
announcement. The output for a valid signature looks like:
gpg: Signature made <DATE> using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team <security@suse.de>"
where <DATE> is replaced by the date the document was signed.
If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command
gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc
Package authenticity verification:
SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.
There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:
Using the internal gpg signatures of the rpm package
MD5 checksums as provided in this announcement
1) The internal 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, replacing <file.rpm> with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.
This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum <filename.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
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
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, the
clear text signature should show proof of the authenticity of the text.
SUSE Linux Products GmbH provides 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>
Security Vulnerability Resolved:
heimdal telnetd remote buffer overflow
Problem Description
Solution or Work-Around
Special Instructions and Notes
Package Location and Checksums
Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
Authenticity Verification and Additional Information
1) Problem Description and Brief Discussion
A remote buffer overflow has been fixed in the heimdal / kerberos
telnetd daemon which could lead to a remote user executing code as
root by overflowing a buffer.
This attack requires the use of the kerberized telnetd of the heimdal
suite, which is not used by default on SUSE systems.
This is tracked by the Mitre CVE ID CAN-2005-2040.
2) Solution or Work-Around
Please install the updated packages.
3) Special Instructions and Notes
Since the heimdal telnetd is usually started from inetd/xinetd,
no action is necessary.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command
rpm -Fhv <file.rpm>
to apply the update, replacing <file.rpm> with the filename of the
downloaded RPM package.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
Announcement authenticity verification:
SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.
To verify the signature of the announcement, save it as text into a file
and run the command
gpg --verify <file>
replacing <file> with the name of the file where you saved the
announcement. The output for a valid signature looks like:
gpg: Signature made <DATE> using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team <security@suse.de>"
where <DATE> is replaced by the date the document was signed.
If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command
gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc
Package authenticity verification:
SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.
There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:
Using the internal gpg signatures of the rpm package
MD5 checksums as provided in this announcement
1) The internal 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, replacing <file.rpm> with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.
This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum <filename.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
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
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, the
clear text signature should show proof of the authenticity of the text.
SUSE Linux Products GmbH provides 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>
The problem can be corrected by upgrading the affected package to
version 4:4.3.8-3ubuntu7.9 (for Ubuntu 4.10), or 4:4.3.10-10ubuntu3.1
(for Ubuntu 5.04). In general, a standard system upgrade is
sufficient to effect the necessary changes.
Details follow:
A remote code execution vulnerability has been discovered in the XMLRPC module
of the PEAR (PHP Extension and Application Repository) extension of PHP. By
sending specially crafted XMLRPC requests to an affected web server, a remote
attacker could exploit this to execute arbitrary code with the web server's
privileges.
In Ubuntu 5.04 (Hoary Hedgehog), the PEAR extension is unsupported (it is
contained in the php4-universe package which is part of universe). However,
since this is a highly critical vulnerability, that package was fixed as well.
Please note that many applications contain a copy of the affected XMLRPC code,
which must be fixed separately. The following packages may also be affected,
but are unsupported in Ubuntu:
drupal
wordpress
phpwiki
horde3
ewiki
egroupware
phpgroupware
These packages might be fixed by the community later.
The following common third party applications are affected as well, but not packaged
for Ubuntu:
Serendipity
Postnuke
tikiwiki
phpwebsite
If you run any affected software, please upgrade them as soon as possible to
protect your server.
