|
BEA WebLogic Server/Express Vulnerabilities and Security Issues
|
|
Secunia Advisory:
|
SA18592
|
|
|
Release Date:
|
2006-01-24
|
|
Last Update:
|
2006-05-16
|
|
Popularity:
|
8,410 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Security Bypass
Exposure of system information
Exposure of sensitive information
DoS
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | BEA WebLogic Express 6.x
BEA WebLogic Express 7.x
BEA WebLogic Express 8.x
BEA WebLogic Express 9.x
BEA WebLogic Server 6.x
BEA WebLogic Server 7.x
BEA WebLogic Server 8.x
BEA WebLogic Server 9.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2006-0422
CVE-2006-0424
CVE-2006-0426
CVE-2006-0427
CVE-2006-0429
CVE-2006-0430
CVE-2006-0431
CVE-2006-0432
|
|
Description:
Multiple vulnerabilities and security issues have been reported in WebLogic Server and WebLogic Express, where the most critical ones potentially can be exploited by malicious people to cause a DoS (Denial of Service), disclose sensitive information, and bypass certain security restrictions.
1) An error in the MBean protection can be exploited by a malicious Java client to access protected MBean attributes or cause DoS on a vulnerable server via RMI (Remote Method Invocation).
The vulnerability affects the following versions:
* WebLogic Server 8.1 through Service Pack 4 (all platforms)
* WebLogic Server 7.0 through Service Pack 6 (all platforms)
* WebLogic Server 6.1 through Service Pack 7 (all platforms)
2) The server log is not properly protected and may be viewed by malicious users.
Successful exploitation requires that the user has been authenticated (there may exist a guest account for domains upgraded from WebLogic Server 6.x).
The security issue affects the following versions:
* WebLogic Server 8.1 through Service Pack 4 (all platforms)
* WebLogic Server 7.0 through Service Pack 6 (all platforms)
* WebLogic Server 6.1 through Service Pack 7 (all platforms)
3) When a password change occurs, the WebLogic Auditing provider writes the old and new password in clear-text to the "DefaultAuditRecorder.log" file and potentially other audit providers' audit stores.
Successful exploitation requires that the site has enabled configuration auditing.
The security issue affects the following versions:
* WebLogic Server 8.1 through Service Pack 4 (all platforms)
4) System passwords are not properly protected from being decrypted. This can be exploited to decrypt system passwords via a malicious application (e.g. EJBs or servlets) installed on the server .
The security issue affects the following versions:
* WebLogic Server 9.0 (all platforms)
* WebLogic Server 8.1 through Service Pack 4 (all platforms)
5) A new security provider, which has been configured, is not activated until the server reboots. This may cause users and security policies to be added or removed to a non-active provider.
The security issue affects the following version:
* WebLogic Server 9.0 (all platforms)
6) The usage of connection filters may in certain situations cause the server performance to decrease.
The security issue affects the following versions:
* WebLogic Server 9.0 (all platforms)
* WebLogic Server 8.1 through Service Pack 5 (all platforms)
* WebLogic Server 7.0 through Service Pack 6 (all platforms)
7) An error in the protection of the server's SSL identity can be exploited to obtain the SSL identity via a malicious application running on the server.
The vulnerability affects the following version:
* WebLogic Server 8.1 Service Pack 5
8) Certain security policies added via the console by the administrator does not properly protect JNDI resources. This may be exploited by malicious people to access certain restricted resources.
The security issue affects the following version:
* WebLogic Server 9.0 (all platforms)
Solution:
Apply patches and service packs (see the original vendor advisories).
Provided and/or discovered by:
Reported by the vendor.
Changelog:
2006-01-30: Added CVE references.
2006-03-21: Vendor issues new patch for security issue #2 (previous patch caused an exception in some environments during system startup).
2006-05-16: Removed SP5 as affected in vulnerability #4.
Original Advisory:
BEA06-109.00:
http://dev2dev.bea.com/pub/advisory/166
BEA06-111.01:
http://dev2dev.bea.com/pub/advisory/179
BEA06-113.00:
http://dev2dev.bea.com/pub/advisory/170
BEA06-114.01:
http://dev2dev.bea.com/pub/advisory/184
BEA06-116.00:
http://dev2dev.bea.com/pub/advisory/173
BEA06-117.00:
http://dev2dev.bea.com/pub/advisory/174
BEA06-118.00:
http://dev2dev.bea.com/pub/advisory/175
BEA06-119.00:
http://dev2dev.bea.com/pub/advisory/176
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
