From: Oracle Corporation
Minor Subject: Principals from a derived Principal class may not be fully validated.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Low
A remote Java client might be used to gain incorrect identity given a specific server configuration.
A derived Principal may be only partially validated which could lead to incorrect identity.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. Upgrades 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 have installed custom Principal classes that inherit from the default BEA Principal classes or other custom Principal classes may be vulnerable. Sites using the WebLogic Authentication providers with the default Principals are not vulnerable.
In some instances it might be possible to have a derived Principal that is only partially validated. This problem can only occur if a Principal has multiple PrincipalValidators that apply to it. A knowledgeable attacker with access to a Java client supporting the derived Principals might be able to tamper with a Principal within a Subject to obtain elevated privileges.
This patch resolves the issue by ensuring that every PrincipalValidator is offered the opportunity to validate Principals it supports.
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.
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.
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: