PM00341: ACCESS TO LOCAL EJB MIGHT BE GRANTED EVEN A SUBJECT HAD BEEN EXPIRED.

Fixes are available

APAR status

Closed as program error.

Error description

When an EJB invokes another EJB which locates in a local
machine, a direct method invocation will be made.

In this scenario, even current caller Subject in an invoker had
been expired, an EJB container of a called method doesn't
validate expiration of the Subject. As a result, although
Subject has been expired in a middle processing an invoker
Subject, this Subject still be treated as a valid Subject for
authorization as long as an invocation is local call.

The expected behavior is that a local EJB invocation with
expired Subject should be rejected.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: When caller Subject had been            *
*                      expired, the Subject can be used for    *
*                      local EJB calls.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
There are couple of issues which leads to this problem.

- return value of isCallerInRole method
isCallerInRole method checks whether role of invocation
Subject is granted to access the resource. But this method
doesn't check whether given Subject is expired or not, prior
to extract Principal from Subject.
As a result, even a given Subject is expired, this method
returns true which means that the given Subject has proper
role to access the resource.
The expected behavior here is that it returns false because
the current user is UNAUTHENTICATED due to expired Subject.

- preInvoke in EJSSecurityCollaborator class

This preInvoke method is invoked upon both remote EJB call and
local EJB call, however, in case of a local EJB call, this
method doesn't check whether given invocation and caller
Subject are not expired prior to continue processing. As a
result, expired Subject might be used for processing EJB.

Problem conclusion

With this fix, a strict Subject expiration check can be used
if following top level security custom property is set:

Name:
com.ibm.websphere.security.strictCredentialExpirationCheck

This property sets behavior of credential expiration checking
method upon local EJB calls.

Value:
true - enforce strict credential expiration check for local
EJB call.
false - no credential expiration check for local EJB call.
this is default.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.31, and 7.0.0.11. Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM00341
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-03
Closed date
2010-01-21
Last modified date
2010-01-21

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PM00341: ACCESS TO LOCAL EJB MIGHT BE GRANTED EVEN A SUBJECT HAD BEEN EXPIRED.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?