Home Infrastructure

Advisories: September 12, 2005

By

September 13, 2005

Debian GNU/Linux

Debian Security Advisory DSA 807-1 security@debian.org
http://www.debian.org/security/
Martin Schulze
September 12th, 2005 http://www.debian.org/security/faq

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.

Debian GNU/Linux 3.0 alias woody

Source archives:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5.dsc

Size/MD5 checksum: 678
42c9d0a0f14e44ba466f2bf07aa91a2f
http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5.diff.gz

Size/MD5 checksum: 18176
ae891738b92b0ba9f59723818f994240
http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9.orig.tar.gz

Size/MD5 checksum: 752613
aad438a4eaeeee29ae74483f7afe9db0

Architecture independent components:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl-doc_2.8.9-2.5_all.deb

Size/MD5 checksum: 288148
c1ac22c913e960e5b3e62360d3486aa3

Alpha architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_alpha.deb

Size/MD5 checksum: 248124
e011a4adbdf97b724ab8a8162217c9a9

ARM architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_arm.deb

Size/MD5 checksum: 240264
bf3f0f685d7d207a17d39e2181ba989e

Intel IA-32 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_i386.deb

Size/MD5 checksum: 239404
eca68ce8bf3e2247e0279c1b3628e60c

Intel IA-64 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_ia64.deb

Size/MD5 checksum: 268944
1ede24bd30b8ea77e0fce6a49010033e

HP Precision architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_hppa.deb

Size/MD5 checksum: 248308
a56a68fb2b0a7ab063602e8c8f3f2538

Motorola 680×0 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_m68k.deb

Size/MD5 checksum: 241318
2fbeb081aef69c28e5f8fc2ecd7db836

Big endian MIPS architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_mips.deb

Size/MD5 checksum: 236352
fbd352506975b03aef5f6e4086774709

Little endian MIPS architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_mipsel.deb

Size/MD5 checksum: 236222
e9961d0c726dda2043871299fa025c06

PowerPC architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_powerpc.deb

Size/MD5 checksum: 242200
3bc5c820ed9d3b1809d155849503ef62

IBM S/390 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_s390.deb

Size/MD5 checksum: 242268
7904cf59c3721ea30e81ef459779ff61

Sun Sparc architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.9-2.5_sparc.deb

Size/MD5 checksum: 244344
482824082ae26b56d7c11a1097594c10

Debian GNU/Linux 3.1 alias sarge

Source archives:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1.dsc

Size/MD5 checksum: 777
aec67b282ab592d34db203410ef5cde6
http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1.diff.gz

Size/MD5 checksum: 30142
52ac6a109d51bd1f62f7cb7377a60d7f
http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22.orig.tar.gz

Size/MD5 checksum: 754606
cdfdf1f576f77768c90825b43b462405

Architecture independent components:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl-doc_2.8.22-1sarge1_all.deb

Size/MD5 checksum: 253078
b3928bc80d9fcbf60a3d0d464be33d4c

Alpha architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_alpha.deb

Size/MD5 checksum: 273382
94b20d48635978fc3d3dd5cc793070dc

AMD64 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_amd64.deb

Size/MD5 checksum: 269692
7fa6da362ad89889e76573298849e1f8

ARM architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_arm.deb

Size/MD5 checksum: 262890
1f7a033007f8b439723f7f7efbb3b03b

Intel IA-32 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_i386.deb

Size/MD5 checksum: 265342
ba6d68db82b12e75ff84e0de13bb665a

Intel IA-64 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_ia64.deb

Size/MD5 checksum: 291062
bb299b74a00d4997f3c44680cce1e5a5

HP Precision architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_hppa.deb

Size/MD5 checksum: 275966
9a9cb9625e8d5f65026a7fb52ce50a18

Motorola 680×0 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_m68k.deb

Size/MD5 checksum: 267556
ddfdc0675713fc0a00787a6e9781e8e4

Big endian MIPS architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_mips.deb

Size/MD5 checksum: 262734
faa260d56b0dea69c27095c062c04ade

Little endian MIPS architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_mipsel.deb

Size/MD5 checksum: 262600
3fbc806ed03c1276f7c210258623beac

PowerPC architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_powerpc.deb

Size/MD5 checksum: 266024
3bae19ace2cd7023bbe5c6d73bf7adcb

IBM S/390 architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_s390.deb

Size/MD5 checksum: 273948
a18d42e87496c31df94b35f2053e729e

Sun Sparc architecture:

http://security.debian.org/pool/updates/main/liba/libapache-mod-ssl/libapache-mod-ssl_2.8.22-1sarge1_sparc.deb

Size/MD5 checksum: 267428
b54b9bba8902ba95470baa6f32738570

These files will probably be moved into the stable distribution
on its next update.

Debian Security Advisory DSA 808-1 security@debian.org
http://www.debian.org/security/
Martin Schulze
September 12th, 2005 http://www.debian.org/security/faq

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.

Debian GNU/Linux 3.1 alias sarge

Source archives:

http://security.debian.org/pool/updates/main/t/tdiary/tdiary_2.0.1-1sarge1.dsc

Size/MD5 checksum: 698
725575945a14b3ff9ff776e4254b6e54
http://security.debian.org/pool/updates/main/t/tdiary/tdiary_2.0.1-1sarge1.diff.gz

Size/MD5 checksum: 24611
df8afbbc86e0f1a9f365a1b8271e7a12
http://security.debian.org/pool/updates/main/t/tdiary/tdiary_2.0.1.orig.tar.gz

Size/MD5 checksum: 1840990
eaec0d3c00e1605d5cefad4119718183

Architecture independent components:

http://security.debian.org/pool/updates/main/t/tdiary/tdiary-contrib_2.0.1-1sarge1_all.deb

Size/MD5 checksum: 109264
b3de14edff72c292002d68b4f6c5234c
http://security.debian.org/pool/updates/main/t/tdiary/tdiary-mode_2.0.1-1sarge1_all.deb

Size/MD5 checksum: 27768
632e5ed6bb82fce0d1f787aea0b25cf4
http://security.debian.org/pool/updates/main/t/tdiary/tdiary-plugin_2.0.1-1sarge1_all.deb

Size/MD5 checksum: 155066
6100fce2dbe0a8acc5a365766b2b8b84
http://security.debian.org/pool/updates/main/t/tdiary/tdiary-theme_2.0.1-1sarge1_all.deb

Size/MD5 checksum: 1506732
6a77d569ef301bc299ee4fe8e4f929f5
http://security.debian.org/pool/updates/main/t/tdiary/tdiary_2.0.1-1sarge1_all.deb

Size/MD5 checksum: 171434
b31846dc0632acdb13787a5ec28e8bc5

These files will probably be moved into the stable distribution
on its next update.

For apt-get: deb http://security.debian.org/
stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security
dists/stable/updates/main
Mailing list: debian-security-announce@lists.debian.org

Package info: `apt-cache show <pkg>’ and http://packages.debian.org/<pkg>

Fedora Core

Fedora Update Notification
FEDORA-2005-860
2005-09-12

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 be downloaded from:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/

00805dac96c841cbfd40170022190619
SRPMS/openssh-4.2p1-fc4.1.src.rpm
0e3920148be386e1ad059a36203a2ad4
ppc/openssh-4.2p1-fc4.1.ppc.rpm
b43f94f610df46c8d2906a1fd9c66426
ppc/openssh-clients-4.2p1-fc4.1.ppc.rpm
5cdd6f0de550be0100118c1e1edda6be
ppc/openssh-server-4.2p1-fc4.1.ppc.rpm
72b2eb642aab64911f129c2f1bbd7c87
ppc/openssh-askpass-4.2p1-fc4.1.ppc.rpm
7dcfd13cedac17596625d9131bb0ec92
ppc/openssh-askpass-gnome-4.2p1-fc4.1.ppc.rpm
3f8eeae5e885288ab0eabba60eab049f
ppc/debug/openssh-debuginfo-4.2p1-fc4.1.ppc.rpm
bc455ca2e0efba438e17b2ee3f558ff2
x86_64/openssh-4.2p1-fc4.1.x86_64.rpm
e92b67a22a9a86f710ba6310de3ba646
x86_64/openssh-clients-4.2p1-fc4.1.x86_64.rpm
5b676585808c1d3dccd4220c13314507
x86_64/openssh-server-4.2p1-fc4.1.x86_64.rpm
eb91cc04ca4e8a72a271a555d40c023b
x86_64/openssh-askpass-4.2p1-fc4.1.x86_64.rpm
ab86ad7914bbf360be0d2356e3727c6d
x86_64/openssh-askpass-gnome-4.2p1-fc4.1.x86_64.rpm
afb0acbb94a568463662ea4af55f4cb6
x86_64/debug/openssh-debuginfo-4.2p1-fc4.1.x86_64.rpm
8863fa64f0bf415de311407840f6ad2d
i386/openssh-4.2p1-fc4.1.i386.rpm
1ab4c1ff99c6ec2975510ad811beeb41
i386/openssh-clients-4.2p1-fc4.1.i386.rpm
8402e25877a6e0d78d960ce53a44250d
i386/openssh-server-4.2p1-fc4.1.i386.rpm
e8ff043f0383a740f391b4c71a4b869a
i386/openssh-askpass-4.2p1-fc4.1.i386.rpm
67991f582615c924a529eb63b9910d29
i386/openssh-askpass-gnome-4.2p1-fc4.1.i386.rpm
3876419031aabbfe4aecc5d1e82dfa11
i386/debug/openssh-debuginfo-4.2p1-fc4.1.i386.rpm

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.

x86 Platform:

x86-64 Platform:

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:
1. Using the internal gpg signatures of the rpm package
2. 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:
- suse-security@suse.com
  General Linux and SUSE security discussion.
  All SUSE security announcements are sent to this list. To
  subscribe, send an e-mail 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 e-mail 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>.

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, 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>

Complete Story

Previous articleZDNet: Against Whom is Linux Competing?

Next articleLinux.com: CLI Magic: The Word on wget

Advisories: September 12, 2005

Debian GNU/Linux

Fedora Core

SUSE Linux

Get the Free Newsletter!

Must Read

Master VLC with These 10+ Expert Tips and Tricks

Xubuntu 24.04 LTS: Best New Features

Slimbook Fedora 2 Is a New Linux Laptop Powered by Fedora 40

EndeavourOS Gemini Lands with the KDE Plasma 6 Desktop Environment

5 Must-Try AI Tools for Linux Users in 2024

Our Brands