Security vulnerability in Solaris Related to the Apache 1.3 mod_perl(3) Module Component "PerlRun.pm" may Lead to Denial of Service (DoS)



Category :Security
Release Phase :Resolved
Bug Id :6738158  
Product :Solaris 8 Operating System
Solaris 9 Operating System
Solaris 10 Operating System  
Date of Workaround Release :14-Jan-2009 
Date of Resolved Release :24-Aug-2009 

Security vulnerability in Solaris related to the Apache 1.3 mod_perl(3) module component "PerlRun.pm" may lead to Denial of Service (DoS):


1. Impact

A security vulnerability in Solaris related to the Apache HTTP server may affect the Apache 1.3 web server bundled with Solaris 8, 9 and 10 . The vulnerability, a Denial of Service(DoS) in the "RunPerl.pm" component of the mod_perl(3) Apache server module, may allow a remote unprivileged user to cause a Denial of Service to the Apache "httpd" process.

Additional information regarding this issue is available at:

2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform
  • Solaris 8 without patch 116973-08
  • Solaris 9 without patch 113146-12
  • Solaris 10 without patch 122911-14
  • OpenSolaris based upon builds snv_01 through snv_99
x86 Platform
  • Solaris 8 without patch 116974-08
  • Solaris 9 without patch 114145-11
  • Solaris 10 without patch 122912-14
  • OpenSolaris based upon builds snv_01 through snv_99
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_86
Note 2:  A system is only vulnerable to this issue if the Apache 1.3 web server has been configured and is running on the system.

To determine if the Apache 1.3 web server is running on the system, the following command can be used:
    $ /usr/bin/ps -ef | grep "/usr/apache/bin/http"
nobody 103892 102307 0 Jan 20 ? 0:27 /usr/apache/bin/httpd
Note 3: This vulnerability only affects systems which make use of the Apache Server mod_perl(3) (PerlRun.pm) component.

To determine if the "PerlRun.pm" component is used, a command such as the following can be run for all configuration files that define the running Apache 1.3 configuration:
    $ grep PerlHandler /etc/apache/httpd.conf | grep Apache::PerlRun
PerlHandler Apache::PerlRun
Note 4: Solaris 8 entered EOSL Phase 2 on 1 April 2009. Entitlement to patches developed on or after 1 April 2009 requires the purchase of the Solaris 8 Vintage Patch Service. See note in section 5 for more details.

3. Symptoms


If the issue is exploited, the Apache 1.3 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
[...]
4. Workaround

To work around the described issue, make sure that the mod_perl(3) (PerlRun.pm) component is not configured in the Apache 1.3 "httpd.conf" file.

5. Resolution

This issue is addressed in the following releases:

SPARC Platform
  • Solaris 8 with patch 116973-08 or later
  • Solaris 9 with patch 113146-12 or later
  • Solaris 10 with patch 122911-14 or later
  • OpenSolaris based upon build snv_100 or later
x86 Platform
  • Solaris 8 with patch 116974-08 or later
  • Solaris 9 with patch 114145-11 or later
  • Solaris 10 with patch 122912-14 or later
  • OpenSolaris based upon build snv_100 or later
Note: The READMEs of Solaris 8 patches developed on or after 1 April 2009 are available to all customers. However, Solaris 8 entered EOSL Phase 2 on April 1, 2009 and thus entitlement for these patches, including those that fix security vulnerabilities, requires the purchase of the Solaris 8 Vintage Patch Service. More information about the Solaris 8 Vintage Patch Service is available at:


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

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

22-Apr-2009: Updated Contributing Factors and Resolution sections.
24-Aug-2009: Updated Contributing Factors and Resolution sections. Resolved.




Attachments
This solution has no attachment

 
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

Search

Article Details
Article ID : 248386
Article Type : Sun Alert
Last reviewed : 2009-09-01
Audience : PUBLIC
Keywords :
Provide feedback  (help)
Page Tools
»  Print This Page
»  Email This Article
»  Bookmark This Article