Bug 870868 (CVE-2012-4549)

Summary:	CVE-2012-4549 JBoss AS: EJB authorization succeeds for any role when allowed roles list is empty
Product:	[Other] Security Response	Reporter:	Arun Babu Neelicattu <aneelica>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	djorm, grocha, pcheung, security-response-team
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-19 01:12:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	876438, 881519

Description Arun Babu Neelicattu 2012-10-29 04:03:11 UTC

When there are no allowed roles for an EJB method invocation, the invocation should be denied for all users. The processInvocation() method in org.jboss.as.ejb3.security.AuthorizationInterceptor incorrectly authorizes all method invocations to proceed when the list of allowed roles is empty.

Comment 2 David Jorm 2012-10-29 04:13:49 UTC

Acknowledgements:

This issue was discovered by Arun Neelicattu of the Red Hat Security Response Team.

Comment 24 errata-xmlrpc 2012-12-18 22:21:55 UTC

This issue has been addressed in following products:

  JBEAP 6 for RHEL 5

Via RHSA-2012:1591 https://rhn.redhat.com/errata/RHSA-2012-1591.html

Comment 25 errata-xmlrpc 2012-12-18 22:33:39 UTC

This issue has been addressed in following products:

  JBEAP 6 for RHEL 6

Via RHSA-2012:1592 https://rhn.redhat.com/errata/RHSA-2012-1592.html

Comment 26 errata-xmlrpc 2012-12-18 22:53:34 UTC

This issue has been addressed in following products:

  JBoss Enterprise Application Platform 6.0.1

Via RHSA-2012:1594 https://rhn.redhat.com/errata/RHSA-2012-1594.html

Comment 27 David Jorm 2013-05-20 07:49:09 UTC

Statement:

This issue did not affect JBoss Enterprise Application Platform versions 4.x and 5.x.