Improper Input Validation in JGroups
JGroups before 4.0 does not require the proper headers for the ENCRYPT and AUTH protocols from nodes joining the cluster, which allows remote attackers to bypass security restrictions and send and receive messages within the cluster via unspecified vectors. Fixes for this issue have been backported to versions 3.6.10.Final and 3.2.16.Final.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-2141US | critical9.8 | — | ||
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 re… | ||||
02
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2016-1435.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1439.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-2035.htmlWEB
- https://access.redhat.com/errata/RHSA-2016:1345WEB
- https://access.redhat.com/errata/RHSA-2016:1346WEB
- https://access.redhat.com/errata/RHSA-2016:1347WEB
- https://access.redhat.com/errata/RHSA-2016:1374WEB
- https://access.redhat.com/errata/RHSA-2016:1376WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan