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
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. |
JGroups | <4.0 | |
JBoss Enterprise Application Platform | =5.2 | |
JBoss Enterprise Application Platform | =6.4 | |
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.
CVE-2016-2141 is classified as a moderate severity vulnerability.
To resolve CVE-2016-2141, upgrade to JGroups version 3.2.16.Final or 3.6.10.Final or later.
CVE-2016-2141 affects JGroups versions prior to 3.2.16.Final and versions between 3.3.0.Alpha1 and 3.6.10.Final.
An attacker can exploit CVE-2016-2141 to bypass security measures and send and receive messages within an affected JGroups cluster.
There is no specific configuration to mitigate CVE-2016-2141; the recommended action is to upgrade to a secure version.