CVE-2016-2141

Description

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.

9.8

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 1.20% Top 25%

Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory jboss.org

Affected: n/a n/a

References

Link	Tags
https://access.redhat.com/errata/RHSA-2016:1347	vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-2035.html	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1389	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1345	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1376	vendor advisory
https://rhn.redhat.com/errata/RHSA-2016-1330.html	vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-1439.html	vendor advisory
https://rhn.redhat.com/errata/RHSA-2016-1331.html	vendor advisory broken link
http://www.securityfocus.com/bid/91481	vdb entry
https://access.redhat.com/errata/RHSA-2016:1434	vendor advisory
https://rhn.redhat.com/errata/RHSA-2016-1328.html	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1433	vendor advisory
https://issues.jboss.org/browse/JGRP-2021	issue tracking vendor advisory
https://access.redhat.com/errata/RHSA-2016:1374	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1432	vendor advisory
https://access.redhat.com/errata/RHSA-2016:1346	vendor advisory
https://rhn.redhat.com/errata/RHSA-2016-1334.html	vendor advisory
https://rhn.redhat.com/errata/RHSA-2016-1333.html	vendor advisory broken link
https://rhn.redhat.com/errata/RHSA-2016-1329.html	vendor advisory broken link
https://rhn.redhat.com/errata/RHSA-2016-1332.html	vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-1435.html	vendor advisory
http://www.securitytracker.com/id/1036165	vdb entry third party advisory broken link
https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html	third party advisory patch
https://lists.apache.org/thread.html/ra18cac97416abc2958db0b107877c31da28d884fa6e70fd89c87384a%40%3Cdev.geode.apache.org%3E	mailing list
https://lists.apache.org/thread.html/rb37cc937d4fc026fb56de4b4ec0d054aa4083c1a4edd0d8360c068a0%40%3Cdev.geode.apache.org%3E	mailing list

Frequently Asked Questions

What is the severity of CVE-2016-2141?: CVE-2016-2141 has been scored as a critical severity vulnerability.
How to fix CVE-2016-2141?: To fix CVE-2016-2141, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-2141 being actively exploited in the wild?: It is possible that CVE-2016-2141 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.