Security Advisories and Notifications


Security Advisory: (BEA04-59.00)

From: Oracle Corporation

Minor Subject: Patches are available to prevent unintended access to web applications.

Product(s) Affected: WebLogic Server and WebLogic Express

Threat level: Low
The vulnerability occurs when a weblogic.xml file is edited through Weblogic Builder or the SecurityRoleAssignmentMBean.

Severity: High
Security for a web application may be unintentionally disabled.

Recently a developer at Redrock Communications (http://www.redrock.com.au) reported a problem that could potentially cause a security vulnerability in certain versions of WebLogic Server and WebLogic Express. Patches are available to correct this problem (see Section II). BEA System treats potential security problems with the highest degree of urgency and does everything possible to ensure the security of all customer assets. 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

This vulnerability affects sites that use WebLogic Builder to edit weblogic.xml files or any site that uses the SecurityRoleAssignmentMBean.toXML() method.

The vulnerability occurs when a weblogic.xml file that contains <security-role-assignment> tags that do not contain any <principal-name> tags is edited through Weblogic Builder or the SecurityRoleAssignmentMBean.toXML method is used. Due to a coding error the <security-role-assignment> tags are removed. Unless these tags are re-entered, the Servlet container assigns defaults for the security roles (the security role defaults to a group of the same name) thus unintentionally granting access to the web application to some users.

Of particular concern are <security-role-assignment> tags that were externally defined. These tags have the following syntax:
<security-role-assignment>
     <role-name>MyRole</role-name>
     <externally-defined/>
</security-role-assignment>
None of these tags have a <principal-name> tag defined. Therefore, WebLogic Builder will delete them.

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

  • WebLogic Server and WebLogic Express version 8.1 through Service Pack 2, on all platforms.
  • WebLogic Server and WebLogic Express version 7.0 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

Any weblogic.xml file that has been edited by Weblogic Builder must be examined to ensure that all of the desired <security-role-assignment> tags are still in the file.

To prevent this problem in the future:

  1. Upgrade to WebLogic Server and WebLogic Express version 8.1 Service Pack 2.
  2. Download and apply the patch #7823708 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.
WebLogic Server version 8.1 Service Pack 3 will include the functionality in this patch.

You can also examine any weblogic.xml file that has been edited by WebLogic Builder and re-enter any <security-role-assignment> tags that have been deleted.


WebLogic Server and WebLogic Express version 7.0

Any weblogic.xml file that has been edited by Weblogic Builder must be examined to ensure that all of the desired <security-role-assignment> tags are still in the file.

To prevent this problem in the future:

  1. Upgrade to WebLogic Server and WebLogic Express version 7.0 Service Pack 5.
  2. Download and apply the patch #7823703 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.
WebLogic Server version 7.0 Service Pack 6 will include the functionality in this patch.

You can also examine any weblogic.xml file that has been edited by WebLogic Builder and re-enter any <security-role-assignment> tags that have been deleted.


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