Security Advisories and Notifications


Security Advisory: (BEA07-125.01)

From: Oracle Corporation

Minor Subject: Internal network information may be externally visible

Product(s) Affected: WebLogic Server and WebLogic Express

This security advisory (BEA07-125.01) contains updated information in Section II.

This security advisory (BEA07-125.01) contains the corrected remedy for this vulnerability on WebLogic Server and WebLogic Express 6.1. A patch is available to resolve this issue.

Please disregard security advisory BEA06-125.00, as this advisory, BEA07-125.01, supersedes it.

Threat level: Low
Internal network addresses might be exposed.

Severity: Low
Exposes address information that might facilitate other forms of exploit.

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

I. Advisory

This advisory addresses multiple information disclosure issues. Although there are no known exploits, the information disclosed might be useful to an attacker:

  • Sites running WebLogic Server or WebLogic Express 7.0 may expose the DNS/IP address to T3 clients. Messages sent via T3 (a WLS internal protocol) can contain DNS information about the message origin and destination hosts. If a T3 connection is established across a firewall that has network address translation (NAT) enabled, some information about the network configuration behind the firewall might be exposed. To reduce the risk of exposure, BEA recommends that you prevent T3 connections from coming through the firewall.

  • Sites running WebLogic Server or WebLogic Express 8.1 are encouraged to use a custom T3 channel with the PublicAddress attribute specified rather than the default channel so that DNS information is not exposed.

  • Sites running WebLogic Server or WebLogic Express 8.1 with NAT configured channels could expose network information. This advisory resolves the issue by hashing internal addresses. However, this solution might not prevent exposure of domain and server names.

  • The GetIORServlet, which is enabled by default on all servers, can expose internal server information. This servlet allows bootstrap addressing information to be published for a running server. The GetIORServlet predates the standard bootstrap mechanism, and is effectively obsolete. This patch resolves the issue by disabling the GetIORServlet by default. You can still enable the GetIORServlet by enabling the IORServletEnabled attribute in the Server Protocols section of the Administration Console.

  • Certain exceptions thrown when invalid XML is passed to the server result in server details being exposed. This advisory resolves the issue by modifying the exceptions so as not to expose server details.

  • When a SOAP fault is thrown for a transaction it includes a stack trace giving host and port information for the Coordinator. This advisory resolves the issue by printing only the transaction Xid in the exception.

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 6, on all platforms
  • WebLogic Server 6.1 released through service pack 7, 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 7.

WebLogic Server and WebLogic Express version 6.1

  1. Upgrade to WebLogic Server and WebLogic Express 6.1 Service Pack 7.
  2. Download and apply the patch #7824156 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.
  3. Place the jar for the patch in the CLASSPATH before the weblogic.jar file.


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