|
BEA WebLogic Products Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA29041
|
|
|
Release Date:
|
2008-02-20
|
|
Last Update:
|
2008-03-11
|
|
Popularity:
|
4,821 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Hijacking
Security Bypass
Cross Site Scripting
Brute force
Exposure of system information
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | BEA WebLogic Express 10.x
BEA WebLogic Express 6.x
BEA WebLogic Express 7.x
BEA WebLogic Express 8.x
BEA WebLogic Express 9.x
BEA WebLogic Portal 10.x
BEA WebLogic Portal 8.x
BEA WebLogic Portal 9.x
BEA WebLogic Server 10.x
BEA WebLogic Server 6.x
BEA WebLogic Server 7.x
BEA WebLogic Server 8.x
BEA WebLogic Server 9.x
BEA WebLogic Workshop 8.x
BEA Workshop for WebLogic 10.x
BEA Workshop for WebLogic 9.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
| | CVE reference: | CVE-2008-0895
CVE-2008-0896
CVE-2008-0897
CVE-2008-0898
CVE-2008-0899
CVE-2008-0900
CVE-2008-0901
CVE-2008-0902
CVE-2008-0903
CVE-2008-0864
CVE-2008-0865
CVE-2008-0866
CVE-2008-0868
CVE-2008-0869
CVE-2008-0870
|
|
Description:
Some vulnerabilities, security issues, and a weakness have been reported in various BEA WebLogic products, which can be exploited by malicious users to conduct script insertion attacks, and by malicious people to conduct session fixation, cross-site scripting, or brute force attacks, disclose sensitive information, or to bypass certain security restrictions.
1) An error in the processing of requests within the "HttpClusterServlet" and "HttpProxyServlet" proxy servlets, when configured with the "SecureProxy" parameter, can potentially be exploited to gain access to certain administrative resources that are only accessible to an administrator.
This is related to vulnerability #2 in:
SA25284
The following versions of WebLogic Server and WebLogic Express are affected:
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
* WebLogic Server 8.1 released through Service Pack 5, on all platforms
* WebLogic Server 7.0 released through Service Pack 7, on all platforms
* WebLogic Server 6.1 released through Service Pack 7, on all platforms
2) Input to unspecified parameters is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
This is related to vulnerability #6 in:
SA15486
The vulnerability is reported in the following versions of WebLogic Server and WebLogic Express:
* WebLogic Server 10.0 released through Maintenance Pack 1, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 2, on all platforms
* WebLogic Server 9.1 GA release, on all platforms.
* WebLogic Server 9.0 GA release, on all platforms.
* WebLogic Server 8.1 released through Service Pack 6, on all platforms.
* WebLogic Server 7.0 released through Service Pack 7, on all platforms.
* WebLogic Server 6.1 released through Service Pack 7, on all platforms.
3) A weakness is caused due to an error in the account lockout, which can be exploited to perform brute force attacks via the servlets "wl_management_internal1/LogfileSearch" (version 7 and 8) and "bea_wls_diagnostics/accessor" (version 9).
The weakness is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10.0 released through Maintenance Pack 1, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 2, on all platforms
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
* WebLogic Server 8.1 released through Service Pack 6, on all platforms
* WebLogic Server 7.0 released through Service Pack 7, on all platforms
4) An error exists in the handling of sessions and can be exploited to hijack a user's session by tricking the user into logging in after following a specially crafted link.
Successful exploitation requires access to the server's console login page.
The vulnerability is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10.0, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 1, on all platforms
* WebLogic Server 8.1 Service Pack 4 through Service Pack 6, on all platforms
5) Unspecified input passed to the WebLogic Server Administration Console is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in an administrative user's browser session in context of an affected site.
The vulnerability is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10.0, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 1, on all platforms
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
6) An unspecified error in the distributed queue feature can be exploited to bypass the security policies defined on a protected distributed queue.
The vulnerability is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10 with no maintenance packs, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 1, on all platforms
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
7) An unspecified error can be exploited to receive messages from a standalone (physical) JMS Topic destination or a member of a secured Distributed Topic member destination.
The vulnerability is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10 with no maintenance packs, on all platforms
* WebLogic Server 9.2 released through Maintenance Pack 1, on all platforms
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
8) A security issue in the handling of content portlets can result in users gaining access to content portlets that are restricted.
9) An error in the handling of https sessions in the Portal Administration Console can lead to redirects via http.
The security issues are reported in the following version of WebLogic Portal:
* WebLogic Portal 10.0, on all platforms
* WebLogic Portal 9.2 released through Maintenance Pack 1, on all platforms
10) An unspecified error in the processing of HTML request headers can potentially be exploited to get unauthorised access to certain application servlets.
The vulnerability is reported in the following version of WebLogic Server and WebLogic Express:
* WebLogic Server 10.0 on all platforms
* WebLogic 9.2 released through 9.2 Maintenance Pack 1, on all platforms
* WebLogic Server 9.1 on all platforms
* WebLogic Server 9.0 on all platforms
* WebLogic Server 8.1 released through Service Pack 6, on all platforms
* WebLogic Server 7.0 released through Service Pack 7, on all platforms
* WebLogic Server 6.1 released through Service Pack 7, on all platforms
11) Input passed to parameters to the NetUI framework is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session context of an affected site.
The vulnerability is reported in the following versions of WebLogic Workshop and BEA Workshop for WebLogic:
* BEA Workshop for WebLogic 10.0, on all platforms
* BEA Workshop for WebLogic 9.2 released through Maintenance Pack 1, on all platforms
* BEA Workshop for WebLogic 9.1, on all platforms
* BEA Workshop for WebLogic 9.0, on all platforms
* WebLogic Workshop 8.1 released through Service Pack 6, on all platforms
12) Database passwords are stored in clear-text in the "config.xml" file and may expose the database password for the RDBMS Authentication provider to malicious users.
Successful exploitation requires that the site has configured the RDBMS Authentication provider.
This is related to vulnerability #1 in:
SA18593
The security issue is reported in the following versions of WebLogic Portal:
* WebLogic Portal 8.1 released through Service Pack 3, on all platforms.
* WebLogic Portal 7.0 Service Pack 4 through Service Pack 7, on all platforms.
13) Input passed to unspecified parameters to certain Groupspace functions is not properly sanitised before being used. This can be exploited to insert arbitrary HTML and script code, which will be executed in another user's browser session in context of an affected site when the malicious data is viewed.
The vulnerability is reported in the following versions of WebLogic Portal:
* WebLogic Portal 10.0, on all platforms
* WebLogic Portal 9.2 released through Maintenance Pack 1, on all platforms
14) Input passed to unspecified parameters to web applications with page flows using the WebLogic Workshop NetUI framework is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
The vulnerability is reported in following versions of WebLogic Workshop:
* WebLogic Workshop 8.1 released through Service Pack 5, on all platforms
15) An unspecified error in the handling of entitlements can be exploited to bypass an entitlement on an instance of a floatable WLP portlet.
The vulnerability is reported in the following version of WebLogic Portal:
* WebLogic Portal 8.1 released through Service Pack 6, on all platforms
16) A security issue in the handling of entitlements on pages can result in the removal of any entitlement policies without notification.
The security issue is reported in the following versions of WebLogic Portal:
WebLogic Portal 8.1 Service Pack 3 through Service Pack 6, on all platforms.
17) An unspecified error within BEA’s web server plugin can potentially be exploited to crash the Sun, IIS, or Apache web server process via a specially crafted URL.
The vulnerability is reported in Plug-ins for WebLogic Server and WebLogic Express dated prior to November 2007.
Solution:
Apply patches (see vendor advisories for details).
Provided and/or discovered by:
The vendor credits:
2) * ACROS Security
* DV Bern AG
* Application Security Inc
* GomoR
4) Mitja Kolsek, ACROS Security
5) Sasa Kos and Mitja Kolsek, ACROS Security
3) Ramón Pinuaga Cascales, S21sec
Changelog:
2008-02-25: Updated vulnerability #3 and added link to "Original Advisory" section.
2008-02-26: Added CVE reference.
2008-03-11: Added link to "Original Advisory" section.
Original Advisory:
BEA:
http://dev2dev.bea.com/pub/advisory/256
http://dev2dev.bea.com/pub/advisory/257
http://dev2dev.bea.com/pub/advisory/258
http://dev2dev.bea.com/pub/advisory/261
http://dev2dev.bea.com/pub/advisory/262
http://dev2dev.bea.com/pub/advisory/263
http://dev2dev.bea.com/pub/advisory/264
http://dev2dev.bea.com/pub/advisory/265
http://dev2dev.bea.com/pub/advisory/266
http://dev2dev.bea.com/pub/advisory/267
http://dev2dev.bea.com/pub/advisory/268
http://dev2dev.bea.com/pub/advisory/269
http://dev2dev.bea.com/pub/advisory/270
http://dev2dev.bea.com/pub/advisory/271
http://dev2dev.bea.com/pub/advisory/273
http://dev2dev.bea.com/pub/advisory/274
http://dev2dev.bea.com/pub/advisory/275
S21sec:
http://www.s21sec.com/avisos/s21sec-040-en.txt
ACROS Security:
http://www.acrossecurity.com/aspr/ASPR-2008-03-11-1-PUB.txt
http://www.acrossecurity.com/aspr/ASPR-2008-03-11-2-PUB.txt
Other References:
SA15486:
http://secunia.com/advisories/15486/
SA18593:
http://secunia.com/advisories/18593/
SA25284:
http://secunia.com/advisories/25284/
|
|
|
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.
|
|
|
10th Oct, 2008
|
New advisories:
|
15 |
|
New vulnerabilities:
|
83 |
|
Updated advisories:
|
41 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 Solutions | More...
|
|
