Subject: SECURITY ADVISORY (CVE-2008-3257) version .01
From: Oracle Corporation
Minor Subject: Patch available for 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.
On July 28, 2008, Oracle published CVE2008-3257 as an early notification of a critical vulnerability in the WebLogic plug-in for Apache. This revised advisory provides a remedy for that vulnerability.
Recently an exploit has been made public 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 supersedes the previous version that provided only workarounds for this vulnerability.
This revision adds information describing how to obtain an updated version of the Apache plug-in to remedy this issue without the use of workarounds.
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:
III. AFFECTED VERSIONSThe following versions of WebLogic Server and WebLogic Express are affected by this vulnerability
- Apache Plug-ins dated prior to July 28, 2008 which implies:
- BEA WebLogic Server 10.0 released through MP1
- BEA WebLogic Server 9.2 released through MP3
- BEA WebLogic Server 9.1
- BEA WebLogic Server 9.0
- BEA WebLogic Server 8.1 released through SP6
- BEA WebLogic Server 7.0 released through SP7
- BEA WebLogic Server 6.1 released through SP7
- BEA WebLogic Server 10.0 released through MP1
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
Oracle strongly recommends the following course of action:
WebLogic Server plug-ins for Apache web server:
1. Download and apply the web server plug-in patch #7825156 from OracleMetaLink as per the instructions below:
• Select the Patches and Updates tab after logging in to OracleMetaLink.
• Click Simple Search.
• In the Search By field, select Patch Number from the list.
• Enter the patch number. The patch number may be different for different product releases and platforms.
• Select the platform (or choose generic as applicable)
• Click Go.
• Click Download to download the patch.
2. Save a copy of your old plug-in and install the appropriate plug-in on your Web Server.
3. Restart your Web Server
Note: The WebLogic plug-in is compatible with all versions of WebLogic Server.
Note: WebLogic Server 10.3 includes this fix.
Oracle recommends that patches, rather than workarounds, be applied to address this vulnerability. In the earlier version of this advisory, Oracle provided the following workarounds for this exploit:
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 4000See: 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 complete 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. 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:
Note: Information about securing WebLogic Server and WebLogic Express can be found at http://edocs.bea.com/wls/docs103/security.html. Specific lockdown information is provided at http://e-docs.bea.com/wls/docs103/lockdown/index.html. We strongly encourage you to review this documentation to ensure your server deployment is securely configured.
As a policy, if there are any security-related issues with any Oracle product, Oracle will distribute an advisory and instructions with the appropriate course of action. Because the security of your site, data, and code is our highest priority, we are committed to communicating all security-related issues clearly and openly.
All previous advisories can be viewed at: http://www.oracle.com/technology/deploy/security/wls-security.
Additional users who wish to register for product advisory distribution should follow the registration directions at: http://www.oracle.com/technology/deploy/security/alerts.htm.
Security issues can be reported to Oracle by following the directions at: