this update should be really fast pushed out
the demo-exploit brings down a 4x2.50GHz machine with 8 GB RAM in some seconds without having the known workarounds or explicit mod_security-Rules in front
-------- Original-Nachricht -------- Betreff: [ANNOUNCEMENT] Apache HTTP Server 2.2.20 Released Datum: Wed, 31 Aug 2011 07:21:33 -0400 Von: Jim Jagielski jim@jaguNET.com Antwort an: dev@httpd.apache.org An: dev@httpd.apache.org
Apache HTTP Server 2.2.20 Released
The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.2.20 of the Apache HTTP Server ("Apache"). This version of Apache is principally a security and bug fix release:
* SECURITY: CVE-2011-3192 (cve.mitre.org) core: Fix handling of byte-range requests to use less memory, to avoid denial of service. If the sum of all ranges in a request is larger than the original file, ignore the ranges and send the complete file. PR 51714.
We consider this release to be the best version of Apache available, and encourage users of all prior versions to upgrade.
Apache HTTP Server 2.2.20 is available for download from:
http://httpd.apache.org/download.cgi
Please see the CHANGES_2.2 file, linked from the download page, for a full list of changes. A condensed list, CHANGES_2.2.20 provides the complete list of changes since 2.2.19. A summary of all of the security vulnerabilities addressed in this and earlier releases is available:
http://httpd.apache.org/security/vulnerabilities_22.html
This release includes the Apache Portable Runtime (APR) version 1.4.5 and APR Utility Library (APR-util) version 1.3.12, bundled with the tar and zip distributions. The APR libraries libapr and libaprutil (and on Win32, libapriconv version 1.2.1) must all be updated to ensure binary compatibility and address many known security and platform bugs.
Apache 2.2 offers numerous enhancements, improvements, and performance boosts over the 2.0 codebase. For an overview of new features introduced since 2.0 please see:
http://httpd.apache.org/docs/2.2/new_features_2_2.html
This release builds on and extends the Apache 2.0 API. Modules written for Apache 2.0 will need to be recompiled in order to run with Apache 2.2, and require minimal or no source code changes.
http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/VERSIONING
When upgrading or installing this version of Apache, please bear in mind that if you intend to use Apache with one of the threaded MPMs (other than the Prefork MPM), you must ensure that any modules you will be using (and the libraries they depend on) are thread-safe.
On Wed, Aug 31, 2011 at 05:39:14PM +0200, Reindl Harald wrote:
this update should be really fast pushed out
the demo-exploit brings down a 4x2.50GHz machine with 8 GB RAM in some seconds without having the known workarounds or explicit mod_security-Rules in front
-------- Original-Nachricht -------- Betreff: [ANNOUNCEMENT] Apache HTTP Server 2.2.20 Released Datum: Wed, 31 Aug 2011 07:21:33 -0400 Von: Jim Jagielski jim@jaguNET.com Antwort an: dev@httpd.apache.org An: dev@httpd.apache.org
Apache HTTP Server 2.2.20 Released
[...snip...]
The security bug is already being tracked: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3192
I'd expect a new package to be issued shortly. Once that happens, if you want to contribute to pushing this out, be ready to test the fixed package and add karma. The process works when people participate.
Am 31.08.2011 19:31, schrieb Paul W. Frields:
On Wed, Aug 31, 2011 at 05:39:14PM +0200, Reindl Harald wrote:
this update should be really fast pushed out
the demo-exploit brings down a 4x2.50GHz machine with 8 GB RAM in some seconds without having the known workarounds or explicit mod_security-Rules in front
-------- Original-Nachricht -------- Betreff: [ANNOUNCEMENT] Apache HTTP Server 2.2.20 Released Datum: Wed, 31 Aug 2011 07:21:33 -0400 Von: Jim Jagielski jim@jaguNET.com Antwort an: dev@httpd.apache.org An: dev@httpd.apache.org
Apache HTTP Server 2.2.20 Released[...snip...]
The security bug is already being tracked: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3192
I'd expect a new package to be issued shortly. Once that happens, if you want to contribute to pushing this out, be ready to test the fixed package and add karma. The process works when people participate
we are in production with > 20 servers on F14 since some hours own packages with optimized build-flags based on the Fedora-SPEC-File
On Wed, Aug 31, 2011 at 08:28:20PM +0200, Reindl Harald wrote:
Am 31.08.2011 19:31, schrieb Paul W. Frields:
On Wed, Aug 31, 2011 at 05:39:14PM +0200, Reindl Harald wrote:
this update should be really fast pushed out
the demo-exploit brings down a 4x2.50GHz machine with 8 GB RAM in some seconds without having the known workarounds or explicit mod_security-Rules in front
-------- Original-Nachricht -------- Betreff: [ANNOUNCEMENT] Apache HTTP Server 2.2.20 Released Datum: Wed, 31 Aug 2011 07:21:33 -0400 Von: Jim Jagielski jim@jaguNET.com Antwort an: dev@httpd.apache.org An: dev@httpd.apache.org
Apache HTTP Server 2.2.20 Released[...snip...]
The security bug is already being tracked: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3192
I'd expect a new package to be issued shortly. Once that happens, if you want to contribute to pushing this out, be ready to test the fixed package and add karma. The process works when people participate
we are in production with > 20 servers on F14 since some hours own packages with optimized build-flags based on the Fedora-SPEC-File
Not sure what this had to do with my reply, but in the meantime you can use the mitigation that Apache sent out. I'm doing that on my own servers for now.
Am 31.08.2011 22:09, schrieb Paul W. Frields:
On Wed, Aug 31, 2011 at 08:28:20PM +0200, Reindl Harald wrote:
Am 31.08.2011 19:31, schrieb Paul W. Frields:
On Wed, Aug 31, 2011 at 05:39:14PM +0200, Reindl Harald wrote:
this update should be really fast pushed out
the demo-exploit brings down a 4x2.50GHz machine with 8 GB RAM in some seconds without having the known workarounds or explicit mod_security-Rules in front
-------- Original-Nachricht -------- Betreff: [ANNOUNCEMENT] Apache HTTP Server 2.2.20 Released Datum: Wed, 31 Aug 2011 07:21:33 -0400 Von: Jim Jagielski jim@jaguNET.com Antwort an: dev@httpd.apache.org An: dev@httpd.apache.org
Apache HTTP Server 2.2.20 Released[...snip...]
The security bug is already being tracked: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3192
I'd expect a new package to be issued shortly. Once that happens, if you want to contribute to pushing this out, be ready to test the fixed package and add karma. The process works when people participate
we are in production with > 20 servers on F14 since some hours own packages with optimized build-flags based on the Fedora-SPEC-File
Not sure what this had to do with my reply, but in the meantime you can use the mitigation that Apache sent out. I'm doing that on my own servers for now
it had to do to say we have 2.2.20 since some hours so the fedora packages are not interesting me really
it was a friendly reminder because on koji a build is even not started and with updates-testing it seems to take a long tiem for a critical fix to get to the users since there is nothing to test
httpd-tools-2.2.20-2.fc14.rh.20110831.x86_64 httpd-2.2.20-2.fc14.rh.20110831.x86_64
File: „/usr/sbin/httpd“ Size: 371680 Blocks: 728 IO Block: 4096 reguläre Datei Device: 811h/2065d Inode: 385752 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2011-08-31 18:11:58.000000000 +0200 Modify: 2011-08-31 18:11:58.000000000 +0200 Change: 2011-08-31 18:29:40.118166712 +0200
On Wed, 31 Aug 2011 22:41:29 +0200 Reindl Harald h.reindl@thelounge.net wrote:
...snip...
it was a friendly reminder because on koji a build is even not started and with updates-testing it seems to take a long tiem for a critical fix to get to the users since there is nothing to test
httpd-tools-2.2.20-2.fc14.rh.20110831.x86_64 httpd-2.2.20-2.fc14.rh.20110831.x86_64
I'm sure the maintainers are testing as fast as they can.
If you read the bug, you will note that this version already has someone reporting that it breaks part of rfc2616. For something as widely used as httpd, care in pushing updates is appreciated by me at least.
In the mean time you can use the workarounds or hope that the upstream version doesn't have issues and use that. ;)
Not sure there's much more to say on this thread...
kevin
-
Kevin Fenzi -
Paul W. Frields -
Reindl Harald