From: Oracle Corporation
Minor Subject: Workaround available to prevent Mbean exposure
Product(s) Affected: WebLogic Server and Express
Threat level: Low
This vulnerability requires RMI access to exploit.
This vulnerability results in the leaking of non-confidential configuration data to anonymous users.
Recently a problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server and Express. Patches are available to correct this problem (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.
By default, the MBeanHome for a site can be gotten by an anonymous user from JNDI. From the MBeanHome, many configuration MBeans can be obtained and examined. Although this does not introduce any known security vulnerabilities, Oracle considers it best security practices to deny any potential attackers access to as much configuration data as possible.
This vulnerability affects sites running a WebLogic Server unless they have previously disabled anonymous admin lookup. To exploit this vulnerability, a user must have RMI access to the site.
The following versions of WebLogic Server and Express are affected by this vulnerability
- WebLogic Server and Express 6.1, 7.0, and 8.1, on all platforms
II. SUGGESTED ACTION
Oracle strongly recommends the following course of actions:
There are three courses of action that can be taken to alleviate the risk presented here:
- 1. Protect portions of the JNDI tree that contain sensitive data using the console. Directions for protecting JNDI entries can be found at http://edocs.bea.com/wls/docs81/secwlres/types.html#1210004. The "weblogic.management.adminhome", "weblogic.management.home.localhome" and "weblogic.management.home" entries are the ones that must be protected.
- On WebLogic Server 7.0 and greater, anonymous access can be disabled by setting the Anonymous Admin Lookup Enabled attribute to false. This can be done by following the directions in the "Viewing MBean Attributes" section of http://e-docs.bea.com/wls/docs81/secmanage/domain.html.
- Denying RMI access to clients. This vulnerability requires RMI to access JNDI. If RMI access can be denied (e.g.: via a firewall) then this vulnerability cannot be exploited.
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: