First published: Wed Mar 02 2016(Updated: )
It was found that JGroups did not require necessary headers for encrypt and auth protocols from new nodes joining the cluster. An attacker could use this flaw to bypass security restrictions, and use this vulnerability to send and receive messages within the cluster, leading to information disclosure, message spoofing, or further possible attacks.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jgroups:jgroups | <3.2.16.Final | 3.2.16.Final |
maven/org.jgroups:jgroups | >=3.3.0.Alpha1<3.6.10.Final | 3.6.10.Final |
redhat/jgroups | <3.6.10. | 3.6.10. |
Redhat Jgroups | <4.0 | |
Red Hat JBoss Enterprise Application Platform | =5.2 | |
Red Hat JBoss Enterprise Application Platform | =6.4 | |
Red Hat JBoss Enterprise Application Platform | =7.0 | |
Red Hat Enterprise Linux | =5.0 | |
Red Hat Enterprise Linux | =6.0 | |
Red Hat Enterprise Linux | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.