Security Advisories and Notifications


Security Advisory: (BEA02-22.00)

From: Oracle Corporation

Minor Subject: Patch available to prevent policy roles and mappings from being ignored in WebLogic Integration 7.0 or in WebLogic Server 7.0 Service Pack 1

Product(s) Affected: BEA WebLogic Platform, WebLogic Integration, WebLogic Server and Express

Threat level:

  WebLogic Integration - high

  WebLogic Server and Express - low

Severity: high

Recently a problem was identified that could potentially cause a security vulnerability in certain versions of BEA WebLogic Integration, WebLogic Server and Express. A patch is available for WebLogic Integration, and both a patch and a workaround are available to correct this problem in WebLogic Server and Express (see section II below). BEA treats such possibilities with the highest degree of urgency and does everything possible to ensure the security of all customer assets. As a result, we strongly suggest the following action:

      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 below.


I. ADVISORY

When using WebLogic Integration 7.0 or 7.0 Service Pack 1, or when migrating web applications to WebLogic Server 7.0 Service Pack 1, a potential security vulnerability exists that can cause web applications to run without security policies being enforced.

The following BEA WebLogic Integration releases are affected by this vulnerability
  • Version: BEA WebLogic Integration 7.0 and 7.0 Service Pack 1.
All installations of WebLogic Integration 7.0 and 7.0 Service Pack 1 have this vulnerability.

The following BEA WebLogic Server and Express releases are affected by this vulnerability
  • Version: VBEA WebLogic Server and Express 7.0 Service Pack 1 when upgrading from BEA WebLogic Server and Express 6.0, 6.1, 7.0 and 7.0.0.1.
This vulnerability only occurs when migrating a web application that uses one of the URL patterns described below to Service Pack 1.


CAUSE

A security vulnerability has been found in WebLogic Server 7.0 Service Pack 1 in Web Applications. In WebLogic Server 7.0.0.1 and earlier releases of WLS there was an undocumented extension to the Servlet mappings in the Servlet 2.3 specification (see section "SRV.11.2 Specification of Mappings"). Namely, URL patterns that begin neither with a "*." nor with a "../Index.html" were treated as if they were prefixed with a "../Index.html". For example:

     - the 7.0 WebLogic Server GA web.xml URL pattern

     *

     is equivalent to the Servlet 2.3 URL pattern

      /*

     - the 7.0 WebLogic Server GA web.xml URL pattern

      foo.jsp

      is equivalent to the Servlet 2.3 URL pattern

      /foo.jsp

     - the 7.0 WebLogic Server GA web.xml URL pattern

      mydir/bar.jsp

      is equivalent to the Servlet 2.3 URL pattern

      /mydir/bar.jsp

While this was an undocumented extension to the Servlet 2.3 specification, many applications, including some WebLogic Server examples, utilized this functionality. In WebLogic Server 7.0 Service Pack 1, this extension stopped working. This means that Web Applications that utilized this extended syntax will not have their role mappings and polices enforced in WebLogic Server 7.0 Service Pack 1.

For WebLogic Server, this problem can be fixed either by changing your web.xml files to include the leading slash (ie: replace patterns that are on the left half of the above table with those that are on the right half of the above table) or by applying the patch described below.

For WebLogic Integration, this problem can be fixed by applying the patch described below.


II. SUGGESTED ACTION

Oracle strongly recommends the following course of actions:

WebLogic Integration 7.0 or 7.0 Service Pack 1
  1. Upgrade to WebLogic Platform 7.0 Service Pack 1 and download and apply the patch #7824636 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.
  2. When WebLogic Platform 7.0 Service Pack 2 is available, you can use that version instead of 7.0 Service Pack 1 and this patch.

For WebLogic Server 7.0 Service Pack 1
  1. Apply the following work around:
    This problem can be fixed by changing your web.xml files to include the leading slash (i.e: replace patterns that are on the left half of the above table with those that are on the right half of the above table).
Or:
  1. Download and apply the patch #7824629 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.
  2. When Service Pack 2 becomes available, you can use that .jar instead of this 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