[<prev] [next>] [day] [month] [year] [list]
Message-ID: <OpenPKG-SA-2004.044__46986.2358681441$1097861602$gmane$org@openpkg.org>
Date: Fri, 15 Oct 2004 17:47:17 +0200
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2004.044] OpenPKG Security Advisory (modssl)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
openpkg-security@...npkg.org openpkg@...npkg.org
OpenPKG-SA-2004.044 15-Oct-2004
________________________________________________________________________
Package: apache (option "with_mod_ssl yes" only)
Vulnerability: information disclosure
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= apache-1.3.31-20041005 >= apache-1.3.31-20041015
OpenPKG 2.1 <= apache-1.3.31-2.1.4 >= apache-1.3.31-2.1.5
OpenPKG 2.0 <= apache-1.3.29-2.0.5 >= apache-1.3.29-2.0.6
Dependent Packages: none
Description:
Hartmut Keil discovered [0] an information disclosure vulnerability
in mod_ssl [1], the SSL/TLS module of the Apache [2] webserver. After
a renegotiation, affected versions of mod_ssl fail to ensure that the
requested cipher suite is actually negotiated. In some configurations
a client may be able to retrieve content using a cipher suite the
server does not consider strong enough. The Common Vulnerabilities
and Exposures (CVE) project assigned the id CAN-2004-0885 [3] to the
problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
apache" and "<prefix>/bin/rpm -qi apache | grep with_mod_ssl". If you
have the "apache" package with option "with_mod_ssl" installed and its
version is affected (see above), we recommend that you immediately
upgrade (see Solution) [4][5].
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[6][7], fetch it from the OpenPKG FTP service [8][9] or a mirror
location, verify its integrity [10], build a corresponding binary RPM
from it [4] and update your OpenPKG installation by applying the binary
RPM [5]. For the current release OpenPKG 2.1, perform the following
operations to permanently fix the security problem (for other releases
adjust accordingly).
$ ftp ftp.openpkg.org
ftp> bin
ftp> cd release/2.1/UPD
ftp> get apache-1.3.31-2.1.5.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig apache-1.3.31-2.1.5.src.rpm
$ <prefix>/bin/rpm --rebuild apache-1.3.31-2.1.5.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/apache-1.3.31-2.1.5.*.rpm
________________________________________________________________________
References:
[0] http://issues.apache.org/bugzilla/show_bug.cgi?id=31505
[1] http://www.modssl.org/
[2] http://www.apache.org/
[3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0885
[4] http://www.openpkg.org/tutorial.html#regular-source
[5] http://www.openpkg.org/tutorial.html#regular-binary
[6] ftp://ftp.openpkg.org/release/2.1/UPD/apache-1.3.31-2.1.5.src.rpm
[7] ftp://ftp.openpkg.org/release/2.0/UPD/apache-1.3.29-2.0.6.src.rpm
[8] ftp://ftp.openpkg.org/release/2.1/UPD/
[9] ftp://ftp.openpkg.org/release/2.0/UPD/
[10] http://www.openpkg.org/security.html#signature
________________________________________________________________________
For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@...npkg.org>" (ID 63C4CB9F) of the
OpenPKG project which you can retrieve from http://pgp.openpkg.org and
hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/
for details on how to verify the integrity of this advisory.
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg@...npkg.org>
iD8DBQFBb/DzgHWT4GPEy58RAiuVAJ9aZSEzvz21fIUlxa7Wc7TyQ9U7egCfXqz8
laFy+rt1jxLscb9qokgm49o=
=Git7
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists