From: Oracle Corporation
Minor Subject: Patch Available for Buffer Overflow in BEA WebLogic Server Proxy Plug-In
Product(s) Affected: BEA WebLogic Server and Express
Threat Level: Low
This security advisory (BEA00-05.01) contains updated information in section II. Please disregard SECURITY ADVISORY BEA00-05.00 as this advisory BEA00-05.01 supersedes it.
It has come to our attention that the BEA WebLogic Server proxy plug-in used to integrate third party Web servers may be vulnerable to a buffer overflow attack. This condition has the potential to lead to a security vulnerability in certain versions of BEA WebLogic Server and Express Web server on all supported platforms. BEA treats such possibilities with the highest degree of urgency and does everything possible to ensure the security of all customer assets. As a result, we strongly suggest the following action:
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 below.
IV. If you would like to report a possible security issue in a BEA product, please send it to the BEA email address listed below.
Recently, Core SDI S.A., an information security firm in Argentina, reported a potential security vulnerability in BEA WebLogic Server and Express version 5.1.0 and 4.5.x. When the URL to a JSP is greater than 2060 characters, and the URL is passed to the BEA WebLogic Server proxy plug-in, a buffer overflow may occur. This buffer overflow may cause a security vulnerability. The potential for a buffer overflow affects the BEA WebLogic Server and Express proxy plug-ins that support Netscape Enterprise Server (NES), Microsoft Internet Information Server (IIS), and Apache Web servers.
The effect of a buffer overflow varies depending on the amount and content of the data within the URI. It is possible that a buffer overflow could cause abnormal termination of the Web server, thus resulting in Denial of Service. In addition, a skilled malicious programmer could use a buffer overflow to download, launch and execute malicious code under the Web server's user account.
This advisory covers the following releases of BEA WebLogic Server and Express:
- Version: BEA WebLogic Server and Express version 5.1.0 and 4.5.x using Netscape Enterprise Server, Microsoft Internet Information Server (IIS), and Apache Web Server on all supported platforms.
The proxy plug-in used to integrate third party Web servers indicated above with BEA WebLogic Server and Express limits the URI path size to 2048 bytes. A defect in the proxy plug-in will cause a buffer overflow when the URI path size exceeds 2048 bytes.
The buffer used to hold the URI path is normally populated with both the value of the PathPrepend argument, if configured in the obj.config file of Netscape Enterprise Server or httpd.conf file of Apache, and followed by the URI path specified by the client. If the URI path specified by the client is long enough, it is possible that the computed URI path is greater than the size of the buffer, thus resulting in an overflow when the value is copied into the buffer. For Microsoft IIS, a client specified URI path exceeding 2048 bytes will cause a buffer overflow.
II. SUGGESTED ACTION
Oracle strongly recommends the following course of actions:
Apply the appropriate patch below:
- Version: BEA WebLogic Server and Express version 5.1 as part of BEA WebLogic Enterprise 5.1.x on all OS platforms
- Version: BEA WebLogic Server and Express 5.1.x on all OS platforms
- Version: BEA WebLogic Server and Express 4.5.2 on all OS platforms
- Version: BEA WebLogic Server and Express 4.5.1 on all OS platforms
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: