apache -- mod_rewrite buffer overflow vulnerability

Description:

The Apache Software Foundation and The Apache HTTP Server Project reports:

An off-by-one flaw exists in the Rewrite module, mod_rewrite, as shipped with Apache 1.3 since 1.3.28, 2.0 since 2.0.46, and 2.2 since 2.2.0.

Depending on the manner in which Apache HTTP Server was compiled, this software defect may result in a vulnerability which, in combination with certain types of Rewrite rules in the web server configuration files, could be triggered remotely. For vulnerable builds, the nature of the vulnerability can be denial of service (crashing of web server processes) or potentially allow arbitrary code execution. This issue has been rated as having important security impact by the Apache HTTP Server Security Team.

This flaw does not affect a default installation of Apache HTTP Server. Users who do not use, or have not enabled, the Rewrite module mod_rewrite are not affected by this issue. This issue only affects installations using a Rewrite rule with the following characteristics:

• The RewriteRule allows the attacker to control the initial part of the rewritten URL (for example if the substitution URL starts with $1)
• The RewriteRule flags do NOT include any of the following flags: Forbidden (F), Gone (G), or NoEscape (NE).

Please note that ability to exploit this issue is dependent on the stack layout for a particular compiled version of mod_rewrite. If the compiler used to compile Apache HTTP Server has added padding to the stack immediately after the buffer being overwritten, it will not be possible to exploit this issue, and Apache HTTP Server will continue operating normally.

The Apache HTTP Server project thanks Mark Dowd of McAfee Avert Labs for the responsible reporting of this vulnerability.

References:

• CERT vulnerability note 395412
• CVE name CVE-2006-3747
• List post: <http://marc.theaimsgroup.com/?l=apache-httpd-announce&m=115409818602955>(search)

Affects:

• apache >=1.3.28 <1.3.36_1
• apache >=2.0.46 <2.0.58_2
• apache >=2.2.0 <2.2.2_1
• apache+mod_perl >=1.3.28 <1.3.36_1
• apache+ipv6 >=1.3.28 <1.3.37
• apache_fp >=0
• ru-apache >=1.3.28 <1.3.37+30.23
• ru-apache+mod_ssl >=1.3.28 <1.3.34.1.57_2
• apache+ssl >=1.3.28 <1.3.34.1.57_2
• apache+mod_ssl >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_accel >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_accel+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_accel+mod_deflate >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_accel+mod_deflate+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_deflate >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_deflate+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp+mod_accel >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp+mod_accel+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp+mod_deflate >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp+mod_deflate+ipv6 >=1.3.28 <1.3.36+2.8.27_1
• apache+mod_ssl+mod_snmp+mod_accel+mod_deflate+ipv6 >=1.3.28 <1.3.36+2.8.27_1

Disclaimer: The data contained on this page is derived from the VuXML document, please refer to the the original document for copyright information. The author of portaudit makes no claim of authorship or ownership of any of the information contained herein.

If you have found a vulnerability in a FreeBSD port not listed in the database, please contact the FreeBSD Security Officer. Refer to "FreeBSD Security Information" for more information.