SecurityTracker.com
Keep Track of the Latest Vulnerabilities
with SecurityTracker!
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


Try our Premium Alert Service
 
Sign Up
Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Instant Alerts
Buy our Premium Vulnerability Notification Service to receive customized, instant alerts
Affiliates
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Partners
Become a Partner and License Our Database or Notification Service





Category:   Application (Web Server/CGI)  >   Oracle WebLogic Vendors:   BEA Systems
BEA WebLogic Server May Return an Unexpected User Identity to Certain RMI Requests
SecurityTracker Alert ID:  1010493
SecurityTracker URL:  http://securitytracker.com/id/1010493
CVE Reference:   GENERIC-MAP-NOMATCH   (Links to External Site)
Date:  Jun 14 2004
Impact:   Modification of user information
Fix Available:  Yes  Vendor Confirmed:  Yes  
Version(s): 6.1, 7.0, and 8.1
Description:   A vulnerability was reported in BEA WebLogic Server and Express in the processing of RMI requests via the IIOP protocol. A client may receive an unexpected user identity.

BEA Systems reported that the documentation that describes the behavior when a remote user logs into a target WebLogic Server multiple times as different users using RMI over IIOP and an RMI request is be executed on the target server when there is no current user associated with the remote client's thread is incorrect.

As a result, any client that expects the documented behavior to occur may get an unexpected user identity in an RMI call.

Impact:   A remote client may receive an unexpected user identity in a response to an RMI request. The specific impact depends on the client implementation.
Solution:   The vendor has provided the following solution information.

For WebLogic Server and WebLogic Express 8.1, read the updated documentation at:
http://e-docs.bea.com/wls/docs81/jndi/jndi.html#478033
and ensure that your client code is written correctly with regards to the updated documentation.

For WebLogic Server and WebLogic Express 7.0, read the updated documentation at:
http://e-docs.bea.com/wls/docs70/jndi/jndi.html#477188
and ensure that your client code is written correctly with regards to the updated documentation.

For WebLogic Server and WebLogic Express 6.1, read the updated documentation at:
http://e-docs.bea.com/wls/docs61/jndi/jndi.html#477126
and ensure that your client code is written correctly with regards to the updated documentation.

Vendor URL:  dev2dev.bea.com/resourcelibrary/advisoriesnotifications/BEA04_62.00.jsp (Links to External Site)
Cause:   State error
Underlying OS:  Linux (Any), UNIX (AIX), UNIX (HP/UX), UNIX (Solaris - SunOS), UNIX (Tru64), Windows (NT), Windows (2000)

Message History:   None.


 Source Message Contents

Subject:  http://dev2dev.bea.com/resourcelibrary/advisoriesnotifications/BEA04_62.00.jsp


http://dev2dev.bea.com/resourcelibrary/advisoriesnotifications/BEA04_62.00.jsp

 > Security Advisory: (BEA04-62.00)

 > From: BEA Systems Inc.

 > Minor Subject: A remedy is available to prevent unexpected user identity

 > Product(s) Affected: WebLogic Server and WebLogic Express

 > Server more than once using RMI over the IIOP protocol.

 > wrong identity

BEA reported a the documentation that describes the behavior when a remote user logs into 
a target WebLogic Server multiple times as different users using RMI over IIOP and an RMI 
request is be executed on the target server when there is no current user associated with 
the remote client's thread is in correct.

As a result, any client that expects the documented behavior to occur may get an 
unexpected user identity in an RMI call.

WebLogic Server and WebLogic Express versions 6.1, 7.0, and 8.1 are affected.

The following solution has been provided [quoted]:

     * For WebLogic Server and WebLogic Express 8.1

       Read the updated documentation at: 
http://e-docs.bea.com/wls/docs81/jndi/jndi.html#478033
       and ensure that your client code is written correctly with regards to the updated 
documentation.

     * For WebLogic Server and WebLogic Express 7.0

       Read the updated documentation at: 
http://e-docs.bea.com/wls/docs70/jndi/jndi.html#477188
       and ensure that your client code is written correctly with regards to the updated 
documentation.

     * For WebLogic Server and WebLogic Express 6.1

       Read the updated documentation at: 
http://e-docs.bea.com/wls/docs61/jndi/jndi.html#477126
       and ensure that your client code is written correctly with regards to the updated 
documentation.

 
 


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2018, SecurityGlobal.net LLC