Security Vulnerabilities in the Apache 2 "mod_perl2" Module Components "PerlRun.pm" and "Status.pm" May Lead to Denial of Service (DoS) or Unauthorized Access to Data

---

Two security vulnerabilities exist in the Apache 2 ...

1. Impact

Two security vulnerabilities exist in the Apache 2 mod_perl2(3) module
components which affect the Apache 2.0 web server bundled with Solaris
10 and the Apache 2.2 web server bundled with OpenSolaris.

The first issue, a Denial of Service (DoS) vulnerability in the "RunPerl.pm"
component (CVE-2007-1349), may allow a remote unprivileged user to
cause a Denial of Service to the Apache 2 "httpd" process.

The second issue, a Cross Site Scripting (CSS or XSS) vulnerability in the
"Status.pm" component (CVE-2009-0796), may allow a remote unprivileged
user to inject arbitrary web script or HTML. This may allow the unprivileged
user to bypass access control and gain access to unauthorized data.

Additional information regarding these issues is available at:

CVE-2007-1349 at:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1349

CVE-2009-0796 at:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0796

2. Contributing Factors

These issues can occur in the following releases:

SPARC Platform

• Solaris 10 without patch 120543-15
  
• OpenSolaris based upon builds snv_01 through snv_123
  

x86 Platform

• Solaris 10 without patch 120544-15
  
• OpenSolaris based upon builds snv_01 through snv_123
  

Note 1: OpenSolaris distributions may include additional bug fixes above
and beyond the build from which it was derived. To determine the base
build of OpenSolaris, the following command can be used:

    $ uname -v
     snv_111

Note 2: Solaris 8 and Solaris 9 do not include support for Apache 2
web server and so they are not impacted by these issues.

Note 3: A system is only vulnerable to the described issues if the
Apache 2 web server has been configured and is running on the system.

The following SMF command can be used to see if the Solaris 10 bundled
Apache 2.0 web server service is enabled:

    $ svcs svc:/network/http:apache2
    STATE          STIME    FMRI
    disabled       Feb_02   svc:/network/http:apache2

The following SMF command can be used to see if the OpenSolaris bundled
Apache 2.2 web server service is enabled:

    $ svcs svc:/network/http:apache22
    STATE          STIME    FMRI
    disabled       Feb_02   svc:/network/http:apache22

Note 4: First vulnerability (CVE-2007-1349) only affects systems which
make use of the Apache 2 Server mod_perl2(3) (PerlRun.pm) component.

To determine if the "PerlRun.pm" component is used, the following
command can be run for all configuration files that define the running
Apache 2 configurations:

For Solaris 10:

    $ grep PerlResponseHandler /etc/apache2/httpd.conf | grep ModPerl::PerlRun
    PerlResponseHandler ModPerl::PerlRun

For OpenSolaris:

    $ grep PerlResponseHandler /etc/apache2/2.2/httpd.conf | grep ModPerl::PerlRun
    PerlResponseHandler ModPerl::PerlRun

Note 5: Second vulnerability (CVE-2009-0796) only affects systems which
make use of the Apache 2 Server mod_perl2(3) (Status.pm) component.

To determine if the "Status.pm" component is used, the following command
can be run for all configuration files that define the running Apache 2 configurations:

For Solaris 10:

    $ grep Apache2::Status  /etc/apache2/httpd.conf
    PerlResponseHandler Apache2::Status

For OpenSolaris:

    $ grep Apache2::Status  /etc/apache2/2.2/httpd.conf
    PerlResponseHandler Apache2::Status

3. Symptoms

If the first issue (CVE-2007-1349) is exploited, the Apache 2 web server
may be unresponsive, possibly consuming all available CPU resources.
Commands such as prstat(1M) can be used to determine the utilization of
system resources:

    $ prstat -s cpu
    [...]

There are no predictable symptoms that would indicate that the second
issue (CVE-2009-0796) has been exploited.

4. Workaround

To work around the described issues, do not configure the mod_perl2(3)
components PerlRun.pm and Status.pm in the Apache 2 "httpd.conf" file.
This may be done by commenting the corresponding sections in the file
("ModPerl::PerlRun" and "Apache2::Status").

5. Resolution

This issues are resolved in the following releases:

SPARC Platform

• Solaris 10 with patch 120543-15 or later
  
• OpenSolaris based upon builds snv_124 or later
  

x86 Platform

• Solaris 10 with patch 120544-15 or later
  
• OpenSolaris based upon builds snv_124 or later
  

For more information on Security Sun Alerts, see Technical Instruction ID 213557:

http://sunsolve.sun.com/search/document.do?assetkey=1-61-213557-1

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

Modification History

02-Dec-2009: Updated Contributing Factors and Resolution sections; now Resolved

Attachments

This solution has no attachment