Package : libapache-mod-ssl
Vulnerability : acl restriction bypass
Problem type : remote
Debian-specific: no
CVE ID : CAN-2005-2700
CERT advisory : VU#744929
BugTraq ID : 14721
A problem has been discovered in mod_ssl, which provides strong
cryptography (HTTPS support) for Apache that allows remote attackers
to bypass access restrictions.
For the old stable distribution (woody) this problem has been fixed in
version 2.8.9-2.5.
For the stable distribution (sarge) this problem has been fixed in
version 2.8.22-1sarge1.
For the unstable distribution (sid) this problem has been fixed in
version 2.8.24-1.
We recommend that you upgrade your libapache-mod-ssl 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.
Package : tdiary
Vulnerability : design error
Problem type : remote
Debian-specific: no
CVE ID : CAN-2005-2411
The tdiary Development Team has discovered a Cross-Site Request
Forgery (CSRF) vulnerability in tdiary, a new generation weblog that
can be exploited by remote attackers to alter the users information.
The old stable distribution (woody) does not contain tdiary packages.
For the stable distribution (sarge) this problem has been fixed in
version 2.0.1-1sarge1.
For the unstable distribution (sid) this problem has been fixed in
version 2.0.2-1.
We recommend that you upgrade your tdiary packages.
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.
Product : Fedora Core 4
Name : openssh
Version : 4.2p1
Release : fc4.1
Summary : The OpenSSH implementation of SSH protocol versions 1 and 2.
Description :
OpenSSH is OpenBSD's SSH (Secure SHell) protocol implementation. SSH
replaces rlogin and rsh, to provide secure encrypted communications
between two untrusted hosts over an insecure network. X11 connections
and arbitrary TCP/IP ports can also be forwarded over the secure
channel. Public key authentication may be used for "passwordless"
access to servers.
This package includes the core files necessary for both the OpenSSH
client and server. To make this package useful, you should also
install openssh-clients, openssh-server, or both.
Update Information:
This security update fixes CAN-2005-2797 and CAN-2005-2798
and resolves a problem with X forwarding binding only on
IPv6 address on certain circumstances.
As it is an upgrade to a newer upstream release there is a
small change in interoperability with ssh clients older than
3.5p1 if they are configured so they insist on compression.
If interoperability with such clients is required, the
"Compression" option must be set to "yes".
Wed Sep 7 2005 Tomas Mraz <tmraz@redhat.com> 4.2p1-fc4.1
upgrade to a new upstream version
don't use X11 port which can't be bound on all IP families (#163732)
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command.
SUSE Linux
SUSE Security Announcement
Package: apache2
Announcement ID: SUSE-SA:2005:051
Date: Mon, 12 Sep 2005 09:00:00 +0000
Affected Products: 9.0, 9.1, 9.2, 9.3
SUSE Linux Enterprise Server 8, 9
Open Enterprise Server 9
Vulnerability Type: local command execution, authentication bypass,
memory consumption
Severity (1-10): 5
SUSE Default Package: yes
Cross-References: CAN-2005-2491
CAN-2005-2728
CAN-2005-2700
Content of This Advisory:
Security Vulnerability Resolved:
integer overflow in PCRE
memory consumption bug in byterange splitting
SSL client-certificate authentication bypass
Problem Description
Solution or Work-Around
Special Instructions and Notes
Package Location and Checksums
Pending Vulnerabilities, Solutions, and Work-Arounds:
none
Authenticity Verification and Additional Information
1) Problem Description and Brief Discussion
This update of apache2 fixes an integer overflow in the PCRE quantifier
parsing which can be triggered by a local untrusted user by using a carefully
crafted regex in a .htaccess file to execute arbitrary code. (CAN-2005-2491)
A memory consumption bug in the byterange handling code (CAN-2005-2728)
was fixed.
And a flaw in mod_ssl which allows to bypass the client-certificate
authentication in a vhost context (CAN-2005-2700) was solved.
2) Solution or Workaround
There are no workarounds known.
3) Special Instructions and Notes
Please restart the Apache web server after the update.
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 Workarounds:
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
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.
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:
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 e-mail to
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>
