Security Advisories and Notifications


Security Advisory: (BEA06-116.00)

From: Oracle Corporation

Minor Subject: Non-active security provider appears active.

Product(s) Affected: WebLogic Server

Threat level: Low
If care is taken during administration then there are no known exploits.

Severity: Low
If care is taken during administration then there are no known exploits.

A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. A patch 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.
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.

I. Advisory

All sites that configure new security providers are susceptible to this issue.

Newly configured security providers appear to be active despite the fact that the server will not use them until after a server reboot.

After configuring a new security provider, an administrator may think the provider is active before a server reboot, as no indication is given that the server is still using the security providers from the last reboot. This may lead an administrator to delete or add users, and delete or add security policies to the new provider which in fact will not take effect until the next server reboot as the server is still using the security providers active at the last server reboot.

This patch resolves the issue by ensuring that the WebLogic Administration Console and WebLogic Scripting Tool properly display a warning that the server must be rebooted before a new security provider becomes active. WebLogic Scripting Tool will now display the correct providers in the runtime tree.

The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability

  • WebLogic Server 9.0 on all platforms.

II. SUGGESTED ACTION


Oracle strongly recommends the following course of actions.

  1. Download the patch #7824366 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.


SECURITY COMMUNICATIONS

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: http://www.oracle.com/technology/software/products/ias/bea_main.html

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: http://www.oracle.com/technology/deploy/security/alerts.htm.

Thank you,
Oracle Corporation