The manufacturer has reported a problem with this product but has yet to publish a solution. CPNI advise that additional care is exercised when using this product.
This Security Alert addresses the security issue CVE-2008-3257, a vulnerability in the Apache Connector component (mod_weblogic) of the Oracle Weblogic Server (formerly BEA WebLogic Server). This vulnerability may be remotely exploitable without authentication, i.e. it may be exploited over a network without the need for a username and password. A knowledgeable and malicious remote user can exploit this vulnerability with resulting availability, integrity and confidentiality impact.
Subject: SECURITY ADVISORY (CVE-2008-3257)
From: Oracle Corporation
Minor Subject: Security vulnerability in WebLogic plug-in for Apache
Product(s) Affected: WebLogic Server and WebLogic Express
Oracle treats potential security problems with a high degree of urgency and endeavors to take appropriate steps to help ensure the security of our customers’ systems. As a result, Oracle strongly suggests the following actions:
I. Read the following advisory.
II. Apply the suggested action.
III. If you know of any additional users interested in future security advisories, please forward them the registration instructions included in this advisory.
I. Description
Recently an exploit has become publicly available which may impact the availability, confidentiality or integrity of WebLogic Server applications which use the Apache web server configured with the WebLogic plug-in for Apache. This vulnerability may be remotely exploitable without authentication, i.e. it may be exploited over a network without the need for a username and password. This note provides information for workarounds for this vulnerability.
A subsequent revision of this note will be issued with information on how to obtain an updated version of the Apache plug-in to remedy this issue without the use of workarounds. This revision will be issued after testing has been completed on that updated plug-in.
II. Impact and CVSS Ratings:
CVSS Severity Score: 10.0 (High)
Attack Range (AV): Network
Attack Complexity (AC): Low
Authentication Level (Au): None
Impact Type: Complete confidentiality, integrity and availability violation
Vulnerability Type: Denial of Service
CVSS Base Score Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)
Usage of CVSS by Oracle:
http://www.oracle.com/technology/deploy/security/cpu/cvssscoringsystem.htm
III. AFFECTED VERSIONS
The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability
- Apache Plug-ins dated prior to July 28 2008 which implies:
- WebLogic Server 10.0 released through Maintenance Pack 1, on all platforms
- WebLogic Server 9.2 released through Maintenance Pack 3, on all platforms
- WebLogic Server 9.1 on all platforms
- WebLogic Server 9.0 on all platforms
- WebLogic Server 8.1 released through Service Pack 6, on all platforms
- WebLogic Server 7.0 released through Service Pack 7 on all platforms
- WebLogic Server 6.1 released through Service Pack 7 on all platforms
Note: Apache servers that are already configured with the mod_security module are protected from this vulnerability by the default core ruleset.
IV. SUGGESTED ACTION
Two workarounds are provided for this vulnerability, which Oracle believes will provide protection against this vulnerability.
Apache LimitRequestLine Parameter
It is possible to configure Apache and avert this vulnerability by rejecting certain invalid requests. To do so, add the following parameter to the httpd.conf file and restart Apache:
LimitRequestLine 4000
See: Apache
LimitRequestLine documentation for more information
Note: This parameter limits the maximum URL length to less than 4000 bytes.
Apache mod_security Module
Oracle believes that the workaround using the LimitRequestLine parameter will provide a workaround for WebLogic users that do not require URLs that exceed 4,000 bytes. If there are cases where the use of the LimitRequestLine parameter is not an option, users may also consider use of mod_security in Apache Web Server environments.
This is available in open source from http://www.modsecurity.org/ to address the vulnerability. The mod_security module need only be installed and enabled in order to provide a workaround for this vulnerability. Oracle recommends evaluation in customer environments prior to usage in production.
Oracle strongly recommends that you backup and comprehensively test the stability of your system upon application of any patch or workaround prior to deleting any of the original file(s) that are replaced by a patch or workaround.
Oracle strongly suggests that customers apply the remedies recommended in all our security advisories. For BEA products, Oracle also urges customers to apply every Service/Maintenance Pack as they are released. Service/Maintenance Packs include a roll-up of all bug fixes for each version of the product, as well as each of the prior Service/Maintenance Packs. Service/Maintenance Packs and information about them can be found at:
WebLogic Server: http://commerce.bea.com/showallversions.jsp?family=WLS
WebLogic Platform: http://commerce.bea.com/showallversions.jsp?family=WLP
Note: Information about securing WebLogic Server and WebLogic Express can be found at http://edocs.bea.com/wls/docs100/security.html. Specific lockdown information is provided at http://edocs.bea.com/wls/docs100/lockdown/index.html. We strongly encourage you to review this documentation to ensure your server deployment is securely configured.
V. SECURITY COMMUNICATIONS
All previous advisories and notifications can be viewed at https://support.bea.com/application_content/product_portlets/securityadvisories/index.html
Additional users who wish to register for BEA product advisory distribution should follow the registration directions at https://support.bea.com/application_content/product_portlets/securityadvisories/index.html
VI. REPORTING SECURITY ISSUES
Security issues for BEA products can be reported to Oracle by following the directions at https://support.bea.com/application_content/product_portlets/securityadvisories/index.html.
If you have any questions or have a need to verify the authenticity of this advisory, please contact Oracle Technical Support for BEA products at support@bea.com
Thank you,
Oracle Corporation
This advisory contains information released by the original author. Some of the information may have changed since it was released. If the issue affects you, it may be prudent to retrieve the advisory from the site of the original source to ensure that you receive the most current information concerning that problem. Reference to any specific commercial product, process, or service by trade name, trademark manufacturer, or otherwise, does not constitute or imply its endorsement, recommendation, or favouring by CPNI.
The views and opinions of authors expressed within this notice shall not be used for advertising or product endorsement purposes. CPNI shall not accept responsibility for any errors or omissions contained within this advisory. In particular, they shall not be liable for any loss or damage whatsoever, arising from or in connection with the usage of information contained within this advisory.
CSIRTUK is a member of the Forum of Incident Response and Security Teams (FIRST) and has contacts with other international Incident Response Teams (IRTs) in order to foster cooperation and coordination in incident prevention, to prompt rapid reaction to incidents, and to promote information sharing amongst its members and the community at large.