Red Hat JBoss Enterprise Application Platform (EAP) 6.1.0 does not properly cache EJB invocations by the EJB client API, which allows remote attackers to hijack sessions by using an EJB client.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Jboss_enterprise_application_platform | Redhat | 6.1.0 (including) | 6.1.0 (including) |
Red Hat JBoss Enterprise Application Platform 6.1 | RedHat | * | |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5 | RedHat | jboss-as-client-all-0:7.2.0-9.Final_redhat_9.ep6.el5 | * |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5 | RedHat | jboss-ejb-client-0:1.0.21-2.Final_redhat_2.ep6.el5 | * |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5 | RedHat | jboss-remote-naming-0:1.0.6-3.Final_redhat_3.ep6.el5 | * |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6 | RedHat | jboss-as-client-all-0:7.2.0-9.Final_redhat_9.ep6.el6 | * |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6 | RedHat | jboss-ejb-client-0:1.0.21-2.Final_redhat_2.ep6.el6 | * |
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6 | RedHat | jboss-remote-naming-0:1.0.6-3.Final_redhat_3.ep6.el6 | * |
Red Hat JBoss Portal Platform 6.1 | RedHat | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: