From: Oracle Corporation
Minor Subject: User was not logged out when a Web application was redeployed.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: Low
A user accessing the default Web application is not logged out when it is redeployed. Subsequently, the user may be able to access the Web application even when the security constraints or security role mappings have been changed to preclude access.
The user may be able to access the Web application without authenticating again.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. An upgrade is 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.This vulnerability occurs in both WebLogic Server and WebLogic Express. Subsequent references in this advisory to WebLogic Server are intended to encompass both products.
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.
Any site that changes security constraints or role mappings in the default Web application when redeploying is susceptible to this vulnerability.
A user authenticates successfully and accesses the default Web application requiring authentication. The Web application is then redeployed. The user's session is not immediately invalidated and authentication is not required again in order for the user to access the Web application.
This patch resolves the issue by requiring a user to authenticate again after the Web application is redeployed.The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability:
- WebLogic Server and WebLogic Express 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 7.0
Upgrade to WebLogic Server and WebLogic Express version 7.0 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: