From: Oracle Corporation
Minor Subject: Patches are available to assist in securing passwords in scripts using the WebLogic Server command-line utilities and Administrative ant tasks.
Product(s) Affected: WebLogic Server and WebLogic Express
This notification applies in both WebLogic Server and WebLogic Express. Throughout the rest of this advisory, references to WebLogic Server apply to both products.
Some of the WebLogic Server command-line utilities and Administrative ant tasks require a username and password to execute properly. When using these utilities, it can be difficult to avoid having clear-text passwords in the script file. The weblogic.Server utility can use the boot.properties file to store encrypted passwords on disk and eliminate the need for clear-text passwords in a script. However, the WebLogic Server command-line utilities and Administrative ant tasks provide no such mechanism.
This notification announces a set of enhancements to the WebLogic Server command-line utilities and Administrative ant tasks that required the system administrator to enter the clear-text password. With these fixes, the WebLogic Server command-line utilities and Administrative ant tasks will now create and read user managed configuration files. Like the boot.properties files, this new capability relies on strong encryption and file system protections to be secure.
This new capability is available for WebLogic Server 6.1, 7.0, and 8.1. As the WebLogic Server command-line utilities have evolved throughout these releases, the feature is implemented differently for each release. See Section II for information specific to each WebLogic Server release affected.
The following versions of WebLogic Server are affected by this notification:
- WebLogic Server 8.1, released through Service Pack 2, on all platforms.
- WebLogic Server 7.0, released through Service Pack 4, on all platforms.
- WebLogic Server 6.1, released through Service Pack 6, on all platforms.
If you want to use the new feature, which provides secure use of the WebLogic Server command-line utilities and Administrative ant tasks, perform the following steps:
WebLogic Server 8.1:
- Upgrade to Service Pack 3 and review the materials provided in http://e-docs.bea.com/wls/docs81/notes/new.html under the heading User Configuration and User Key Files for weblogic.Admin and Ant Tasks
WebLogic Server 7.0:
- Upgrade to Service Pack 5 and review the materials provided in http://e-docs.bea.com/wls/docs70/programming/deploying.html under the heading weblogic.Deployer Utility
WebLogic Server 6.1:
- Upgrade to Service Pack 6 and download and apply the patch #7823681 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.
WebLogic Server 6.1 Service Pack 7 will include the functionality in this patch.
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: