From: Oracle Corporation
Minor Subject: Exporting security policies from one operating system and importing to another operating system can lead to servlets being unprotected.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Low
A system administrator who exports security policies from one operating system and then imports them to a different operating system may leave servlets unprotected.
Servlets could be unprotected.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. Documentation updates 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.
All sites are susceptible to this vulnerability. The vulnerability only occurs when system administrators export and import security policies between operating systems. By default, the context path and uri arguments for the WebLogic URLResource (used to protect servlets) are stored in lowercase on Windows and mixed case on UNIX. As a result, if you define security roles and policies in a domain on one operating system, export them, and then import them to a domain on an operating system with different case handling, the security roles and policies may not work correctly. The end result is that Web Application pages that are protected on one operating system may not be protected on a different operating system.
This issue was resolved by updating Managing WebLogic Server to caution system administrators who are exporting and importing policies between different operating systems to the risks involved. The information is available from:
WebLogic Server 7.0
WebLogic Server 8.1
The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability
- WebLogic Server 8.1, on all platforms.
- WebLogic Server 7.0, on all platforms.
II. SUGGESTED ACTION
Oracle strongly recommends the following course of actions.
If you have exported and imported security policies between operating systems, review the appropriate documentation links above to ensure that security roles and policies are entered properly.
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: