From: Oracle Corporation
Minor Subject: Sensitive system properties values are displayed in the server log.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Low
An attacker must have read access to the server log to see the sensitive values.
Passwords supplied to system properties at server boot time could be used to compromise the server.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. Upgrades 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 -D switch to specify system properties with sensitive data are subject to this vulnerability. The vulnerability occurs when system properties with sensitive values (for example, passwords and keystore passwords) are supplied on the Java command-line when booting the server. The values are displayed in the server log as part of server startup. An attacker with read access to the server log could obtain the sensitive values and use them to attack the server. The issue was resolved by replacing the values of the sensitive system properties in the server log file with multiple * characters.
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 5, on all platforms.
- WebLogic Server 6.1 released through Service Pack 7, 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 service pack 6.
WebLogic Server and WebLogic Express version 6.1
- Upgrade to WebLogic Server and WebLogic Express 6.1 Service Pack 7.
- Download and apply the patch #7824755 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: