From: Oracle Corporation
Minor Subject: In specific circumstances, weblogic.Deployer communication with the Administration server could be compromised.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Medium
weblogic.Deployer commands executed over a network could be snooped or spoofed given specific circumstances.
Administrative usernames and passwords could be compromised.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. An upgrade and a patch are available to correct this problem (see Section II). 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.
Sites that use the weblogic.Deployer command with the t3 protocol across an unsecured network may be vulnerable. Even if the Administration port was enabled on the Administration server it was possible for a Deployer to use the weblogic.Deployer command using the t3 protocol instead of the secure t3s protocol. Communication traffic between the weblogic.Deployer command and the Administration server might be vulnerable to snooping.
This patch resolves the issue by throwing a SecurityException if weblogic.Deployer connections to the Administration server use the t3 protocol when the Administration port is enabled.
The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability
- WebLogic Server 8.1 released through Service Pack 4, on all platforms.
- WebLogic Server 7.0 released through Service Pack 6, on all platforms.
II. SUGGESTED ACTION
Oracle strongly recommends the following course of actions.
WebLogic Server and WebLogic Express version 8.1
- Upgrade to service pack 5.
WebLogic Server and WebLogic Express version 7.0
- Upgrade to WebLogic Server and WebLogic Express 7.0 Service Pack 6.
- Download and apply the patch #7824779 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.
- Place the jar for the patch in the CLASSPATH before the weblogic.jar file.
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: