From: Oracle Corporation
Minor Subject: The documentation has been updated to recommend multiple administrator accounts.
Product(s) Affected: WebLogic Server and WebLogic Express
Threat level: High
A remote user could prevent the admin user from logging into the server.
The admin user could be prevented from logging into the server.
A problem was identified that could potentially cause a security vulnerability in certain versions of WebLogic Server. Updated documentation 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.
All sites are susceptible to this vulnerability.
WebLogic Server implements a user lockout mechanism to prevent brute-force attacks. After a certain number of invalid login attempts, WebLogic Server automatically locks the user account. A remote user who knows the name of the admin user could make continuous invalid login attempts in an effort to lock out that user. No data would be compromised and admin users already logged in would still be able to carry out administrative functions.
This advisory resolves the issue by updating the documentation to suggest that there be more than one admin user created and that the name of the user account not be a name that could be easily guessed by an attacker.
For more information see:
II. SUGGESTED ACTION
Oracle strongly recommends the following course of actions.
- WebLogic Server 9.0
Review the documentation on securing the WebLogic Server Security Service — http://edocs.bea.com/wls/docs90/lockdown/practices.html#1137839
- WebLogic Server 8.1
Review the documentation on securing the WebLogic Server Host — http://edocs.bea.com/wls/docs81/lockdown/practices.html#1134923
- WebLogic Server 7.0
Review the documentation on securing the WebLogic Server Host — http://edocs.bea.com/wls/docs70/lockdown/practices.html#1136687
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: