From: BEA Systems Inc.
Minor Subject: Patches are available to prevent unauthorized access
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Medium
Any client that can access a JNDI server can exploit this vulnerability.
Severity: High
The WebLogic Server instance can be rendered unusable and potentially confidential data can be stolen.
Recently a problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server and WebLogic Express. Patches are available to correct this problem (see section II). BEA Systems 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.This vulnerability occurs in both WebLogic Server and WebLogic Express. Throughout the rest of this advisory, references to WebLogic Server apply to both products.
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.
I. ADVISORY
This vulnerability occurs because some internal WebLogic Server objects that are bound into the JNDI tree and are insufficiently protected. Some of these objects control key functions of the server. Simply unbinding the appropriate objects will render the server unreachable (denial-of-service attack). It may be possible through clever coding to leave the server operational but to have some confidential data transmitted to an attacker's object rather than the internal WebLogic Server object for which it was intended.
This security vulnerability affects all installations of the affected releases. Access to the JNDI tree is required to exploit it. The patches available in this security advisory address this vulnerability.
The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability:
- WebLogic Server 8.1, released through Service Pack 2, on all platforms
- WebLogic Server 7.0, released through Service Pack 5, on all platforms
- WebLogic Server 6.1, released through Service Pack 6, on all platforms
II. SUGGESTED ACTION
BEA strongly recommends the following course of actions:
- For WebLogic Server 8.1: Upgrade to WebLogic Server 8.1 Service Pack 3.
- For WebLogic Server 7.0 perform the following steps:
-
- Upgrade to WebLogic Server 7.0 Service Pack 5
- Download the archiveftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/70sp5patch.zip
- Follow the instructions in the readme file to apply the .jar files to your installation.
WebLogic Server 7.0 Service Pack 6 will include the functionality in this patch.
- For WebLogic Server 6.1 perform the following steps:
-
- Upgrade to Service Pack 6
- apply the patchftp://anonymous:dev2dev%40bea.com@ftpna.bea.com/pub/releases/security/CR045135_61sp6.jar
WebLogic Server 6.1 Service Pack 7 will include the functionality in this patch.
BEA Systems strongly suggests that customers apply the remedies recommended in all our security advisories. BEA Systems also urges customers to apply every Service Pack as they are released. Service Packs include a roll-up of all bug fixes for each version of the product, as well as each of the prior Service Packs. Service Packs and information about them can be found at:
http://commerce.beasys.com/downloads/weblogic_server.jsp#wls
Note: Information about securing BEA WebLogic Server and WebLogic Express can be found in Securing a Production Environment at http://e-docs.bea.com/wls/docs81/lockdown/index.html.
BEA Systems strongly encourage you to review this documentation so that you can be assured that your server deployment is securely configured.
III. FUTURE SECURITY COMMUNICATIONS
As a policy, if there are any security-related issues with any BEA product, BEA Systems 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://dev2dev.bea.com/advisoriesnotifications/.
BEA Systems has established an opt-in emailing list specifically targeted for product security advisories. As a policy, if a user has opted-in to our emailing list and there are any security issues with the BEA product(s) he/she is using, BEA Systems will distribute an advisory and instructions via email with the appropriate course of action.
ADDITIONAL USERS WHO WISH TO REGISTER FOR ADVISORY DISTRIBUTION SHOULD FOLLOW THE REGISTRATION DIRECTIONS AT http://dev2dev.bea.com/advisoriesnotifications/.
IV. REPORTING SECURITY ISSUES
Security issues can be reported to BEA by sending email to secalert@bea.com or by following the directions at http://dev2dev.bea.com/advisoriesnotifications/. All reports of security issues will be promptly reviewed and all necessary actions taken to ensure the continued security of all customer assets.
If you have any questions or care to verify the authenticity of this advisory, please contact BEA Technical Support at support@bea.com.



