what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

BEA Systems Security Advisory 04-64.00

BEA Systems Security Advisory 04-64.00
Posted Jun 29, 2004
Authored by Oracle | Site dev2dev.bea.com

A security issue has been discovered in BEA WebLogic, potentially allowing unauthorised users to access affected web applications. Due to improper filtering of data, an asterisk may be used in a spot to allow for a random user to get loaded into a role. The issue affects WebLogic Server and WebLogic Express version 8.1 and 7.0.

tags | advisory, web
SHA-256 | 7dbb3e1ef8269fddff36b4231c3c003fb8a07bf8f1ece8e1cfcd8c3cb95191b5

BEA Systems Security Advisory 04-64.00

Change Mirror Download
<b>Security Advisory:</b> (BEA04-64.00)<br><br>
<b>From:</b> BEA Systems Inc.
<br><br>
<b>Minor Subject:</b> Patches available to protect Web Applications
<br><br>
<b>Product(s) Affected:</b> WebLogic Server and WebLogic Express
<br><br> Threat level: Low - Relies on the use of a relatively obscure
portion of the Servlet 2.3 specification in the Web application’s
deployment descriptor. <br><br>

Severity: Low - A successful exploitation can result in some application security being bypassed.

<br><br> Recently a problem was identified that could potentially cause
a security vulnerability in certain versions of WebLogic Server and
WebLogic Express. Patches are available to correct this problem (see
Section II). BEA System treats potential security problems with the
highest degree of urgency and does everything possible to ensure the
security of all customer assets. As a result, BEA systems strongly
suggests the following actions: <blockquote>
I. Read the following advisory.<br>
II. Apply the suggested action.<br>
III. If you know of any additional users interested in future security
advisories, please forward them the registration instructions below. </blockquote>
<br>

<h3>I. Advisory</h3>
This vulnerability can occur when a Web application has specified a role of name * in a <code>&LTrole-name></code> tag contained within a <code>&LTsecurity-constraint></code> tag. The following code text from a <code>web.xml</code> file exhibits the problematic use of *:
<br><br>
<pre> &LTsecurity-constraint>
&LTweb-resource-collection>
&LTweb-resource-name>myProtectedResourec</web-resource-name>
&LTurl-pattern>/my/secure/urls</url-pattern>
</web-resource-collection>
&LTauth-constraint>
&LTrole-name>*</role-name>
</auth-constraint>
</security-constraint>
</pre>
<br> The Servlet 2.3 specification (section SRV.13.3) specifies that a
role name of * “is a compact syntax for indicating all roles in the web
application”. However, WebLogic Server implements it as a compact
syntax for any user. This difference means that users who have no
defined roles in a Web application can still access resources protected
with a role name of *. <br><br> The provided patch alters the default behavior of the Web
container so that it now interprets * as defined in the Servlet
specification. <br><br>

<b>The following versions of WebLogic Server and WebLogic Express are affected by this vulnerability</b>
<ul>
<li>WebLogic Server and WebLogic Express 8.1, released through Service Pack 2, on all platforms</li>
<li>WebLogic Server and WebLogic Express 7.0, released through Service Pack 5, on all platforms</li>
</ul>

<h3>II. SUGGESTED ACTION</h3>

BEA Systems strongly recommends the following course of actions.
<br><br>

For WebLogic Server and WebLogic Express version 8.1 or WebLogic Server and WebLogic Express version 7.0
<ul>
<li>Remove the * role name from all <code>web.xml</code> files
where the intended meaning of * was to restrict users who are not in
roles defined in the current Web application. Replace this with a <code>&LTrole-name></code> tag for each role defined in the <code>web.xml</code> file.</li>
</ul>
<br>

Or
<br><br>
For WebLogic Server and WebLogic Express version 8.1

<ul>
<li>Upgrade to Service Pack 2 and apply the patch available from:<br>
<a href="ftp://ftpna.beasys.com/pub/releases/security/CR175310_810sp2.jar">ftp://ftpna.beasys.com/pub/releases/security/CR175310_810sp2.jar</a>
<br><br>

WebLogic Server version 8.1 Service Pack 3 will include the functionality in this patch.
</li>
</ul>
<br><br>

For WebLogic Server and WebLogic Express version 7.0
<ul>
<li>Upgrade to Service Pack 5 and apply the patch available from:<br>
<a href="ftp://ftpna.beasys.com/pub/releases/security/CR175310_700sp5.jar">ftp://ftpna.beasys.com/pub/releases/security/CR175310_700sp5.jar</a>
<br><br>

WebLogic Server version 7.0 Service Pack 6 will include the functionality in this
patch.</li>
</ul>
<br><br>

<b>BEA strongly suggests that customers apply the remedies recommended in all our security advisories.</b>
BEA also urges customers to apply every Service Pack as they are
released. Service Packs include a roll-up of all bug fixes for each
version of the product, as well as each of the prior Service Packs.
Service Packs and information about them can be found at: <br><br>
<a href="http://commerce.beasys.com/downloads/weblogic_server.jsp#wls">http://commerce.beasys.com/downloads/weblogic_server.jsp#wls </a>
<br><br>
<b>Note:</b> Information about securing WebLogic Server and WebLogic Express can be found at <a href="http://e-docs.bea.com/wls/docs81/security.html">http://e-docs.bea.com/wls/docs81/security.html</a>, Specific lockdown information is provided at <a href="http://e-docs.bea.com/wls/docs81/lockdown/index.html">http://e-docs.bea.com/wls/docs81/lockdown/index.html</a>. We strongly encourage you to review this documentation to ensure your server deployment is securely configured.
<br><br>
<h3>III. FUTURE SECURITY COMMUNICATIONS</h3> As a corporate policy, if
there are any security-related issues with any BEA product, BEA Systems
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. <br><br>
All previous advisories and notifications can be viewed at <a href="http://dev2dev.bea.com/advisories/">http://dev2dev.bea.com/advisories/</a>
<br><br> BEA Systems has established an opt-in emailing list
specifically targeted for product security advisories and
notifications. As a policy, if a user has opted-in to our emailing list
and there are any security issues with the BEA product(s) he/she is
using, BEA will distribute an advisory and instructions via email with
the appropriate course of action. <br><br>
ADDITIONAL USERS WHO WISH TO REGISTER FOR ADVISORY DISTRIBUTION SHOULD FOLLOW THE REGISTRATION DIRECTIONS AT <a href="http://dev2dev.bea.com/advisories">http://dev2dev.bea.com/advisories</a>

<br><br>
<h3>IV. REPORTING SECURITY ISSUES</h3>
Security issues can be reported to BEA by sending email to <a href="mailto:secalert@bea.com">secalert@bea.com</a> or by following the directions at <a href="http://dev2dev.bea.com/advisories/">http://dev2dev.bea.com/advisories/</a>.
All reports of security issues will be promptly reviewed and all
necessary actions taken to ensure the continued security of all
customer assets. <br><br>
If you have any questions or care to verify the authenticity of this advisory, please contact BEA Technical Support at <a href="mailto:support@bea.com">support@bea.com</a>
<br><br>
Thank you,<br>
BEA Systems, Inc.
<br><br>
</div>




</div>
<div id="footer">
<a href="http://www.bea.com/contact/index.shtml">Contact BEA</a>   
<a href="http://dev2dev.bea.com/sitemap/index.jsp">Site Map</a>   
<a href="http://dev2dev.bea.com/index.xml">RSS</a>   
<a href="http://dev2dev.bea.com/surveys/">Feedback</a>   
<a href="http://www.bea.com/framework.jsp?CNT=privacy.htm&FP=/content/legal/">Privacy</a>   
© 2004 BEA Systems   
<a href="http://dev2dev.bea.com.cn/"><img src="BEA04_64.00_files/intl_cn.gif" alt="dev2dev China"></a>   
<a href="http://www.beasys.co.jp/dev2dev/"><img src="BEA04_64.00_files/intl_jp.gif" alt="dev2dev Japan"></a>

<div class="twodots"><img src="BEA04_64.00_files/_.gif" width="300" height="4" alt=""></div>
<div class="redline"><img src="BEA04_64.00_files/_.html" width="200" height="4" alt=""></div>
</div>



<!-- START OF Data Collection Server TAG -->
<script language="JavaScript" src="BEA04_64.00_files/wt_util.js"></script>
<script language="JavaScript">
<!--
dcs_TAG(TagPath);
//-->
</script>
<noscript>
<img border="0" name="DCSIMG" width="1" height="1" src="http://63.96.161.95/njs.gif?dcsuri=/nojavascript">
</noscript>
<!-- END OF Data Collection Server TAG -->


</body></html>
Login or Register to add favorites

File Archive:

March 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    0 Files
  • 3
    Mar 3rd
    0 Files
  • 4
    Mar 4th
    32 Files
  • 5
    Mar 5th
    28 Files
  • 6
    Mar 6th
    42 Files
  • 7
    Mar 7th
    17 Files
  • 8
    Mar 8th
    13 Files
  • 9
    Mar 9th
    0 Files
  • 10
    Mar 10th
    0 Files
  • 11
    Mar 11th
    15 Files
  • 12
    Mar 12th
    19 Files
  • 13
    Mar 13th
    21 Files
  • 14
    Mar 14th
    38 Files
  • 15
    Mar 15th
    15 Files
  • 16
    Mar 16th
    0 Files
  • 17
    Mar 17th
    0 Files
  • 18
    Mar 18th
    10 Files
  • 19
    Mar 19th
    32 Files
  • 20
    Mar 20th
    46 Files
  • 21
    Mar 21st
    16 Files
  • 22
    Mar 22nd
    13 Files
  • 23
    Mar 23rd
    0 Files
  • 24
    Mar 24th
    0 Files
  • 25
    Mar 25th
    12 Files
  • 26
    Mar 26th
    31 Files
  • 27
    Mar 27th
    19 Files
  • 28
    Mar 28th
    42 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close