Lucene search

K
securityvulnsSecurityvulnsSECURITYVULNS:DOC:11170
HistoryJan 24, 2006 - 12:00 a.m.

[SA18592] BEA WebLogic Server/Express Vulnerabilities and Security Issues

2006-01-2400:00:00
vulners.com
11

TITLE:
BEA WebLogic Server/Express Vulnerabilities and Security Issues

SECUNIA ADVISORY ID:
SA18592

VERIFY ADVISORY:
http://secunia.com/advisories/18592/

CRITICAL:
Moderately critical

IMPACT:
Security Bypass, Exposure of system information, Exposure of
sensitive information, DoS

WHERE:
>From remote

SOFTWARE:
BEA WebLogic Server 9.x
http://secunia.com/product/5822/
BEA WebLogic Server 8.x
http://secunia.com/product/1360/
BEA WebLogic Server 7.x
http://secunia.com/product/754/
BEA WebLogic Server 6.x
http://secunia.com/product/753/
BEA WebLogic Express 9.x
http://secunia.com/product/5823/
BEA WebLogic Express 8.x
http://secunia.com/product/1843/
BEA WebLogic Express 7.x
http://secunia.com/product/1282/
BEA WebLogic Express 6.x
http://secunia.com/product/1281/

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 5 (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 vendor.

ORIGINAL ADVISORY:
1) http://dev2dev.bea.com/pub/advisory/166
2) http://dev2dev.bea.com/pub/advisory/168
3) http://dev2dev.bea.com/pub/advisory/170
4) http://dev2dev.bea.com/pub/advisory/171
5) http://dev2dev.bea.com/pub/advisory/173
6) http://dev2dev.bea.com/pub/advisory/174
7) http://dev2dev.bea.com/pub/advisory/175
8) http://dev2dev.bea.com/pub/advisory/176


About:
This Advisory was delivered by Secunia as a free service to help
everybody keeping their systems up to date against the latest
vulnerabilities.

Subscribe:
http://secunia.com/secunia_security_advisories/

Definitions: (Criticality, Where etc.)
http://secunia.com/about_secunia_advisories/

Please Note:
Secunia recommends that you verify all advisories you receive by
clicking the link.
Secunia NEVER sends attached files with advisories.
Secunia does not advise people to install third party patches, only
use those supplied by the vendor.