# CVE-2016-2141: Improper Input Validation in JGroups > An attacker can bypass JGroups security protocols to send and receive cluster messages, leading to information disclosure and spoofing. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Jun 2016 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2016-2141, GHSA-rc7h-x6cq-988q, RHSA-2016:1328, RHSA-2016:1330, RHSA-2016:1332, UBUNTU-CVE-2016-2141 ## What is CVE-2016-2141? CVE-2016-2141 is a critical vulnerability in Redhat Jboss Enterprise Application Platform, published on 30 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. ## Which versions are affected by CVE-2016-2141? 4 open source packages ship an affected version, including org.jgroups:jgroups. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jgroups:jgroups` | Maven | All versions | 3.2.16.Final | | `org.jgroups:jgroups` | Maven | All versions | 3.2.16.Final | | `org.jgroups:jgroups` | Maven | From 3.3.0.Alpha1 | 3.6.10.Final | | `org.jgroups:jgroups` | Maven | From 3.3.0.Alpha1 | 3.6.10.Final | | `jgroups` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 1:2.6.22-2.ep5.el4 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 1:2.6.22-2.ep5.el5 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 1:2.6.22-2.ep5.el6 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 1:3.2.16-1.Final_redhat_1.1.ep6.el5 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:6::el6 | All versions | 1:3.2.16-1.Final_redhat_1.1.ep6.el6 | | `jgroups` | Red Hat:jboss_enterprise_application_platform:6::el7 | All versions | 1:3.2.16-1.Final_redhat_1.1.ep6.el7 | | `eap7-jgroups` | Red Hat:jboss_enterprise_application_platform:7::el6 | All versions | 0:3.6.8-3.Final_redhat_3.1.ep7.el6 | | `eap7-jgroups` | Red Hat:jboss_enterprise_application_platform:7::el7 | All versions | 0:3.6.8-3.Final_redhat_3.1.ep7.el7 | Products: Redhat Jboss Enterprise Application Platform, Redhat Jgroups. ## How do I fix CVE-2016-2141? Upgrade org.jgroups:jgroups to a fixed version for your release line: 3.2.16.Final or 3.6.10.Final. ## Is CVE-2016-2141 being exploited? There is no known exploitation of CVE-2016-2141 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Jboss Enterprise Application Platform - [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild) - [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild) - [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8) - [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-2141 and fix it if it is affected. What it is: CVE-2016-2141 is a critical vulnerability in Redhat Jboss Enterprise Application Platform, published on 30 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-2141 in the wild and no public exploit code. Affected packages and fixed versions: - org.jgroups:jgroups (Maven): affected all versions; fixed in 3.2.16.Final - org.jgroups:jgroups (Maven): affected all versions; fixed in 3.2.16.Final - org.jgroups:jgroups (Maven): affected from 3.3.0.Alpha1; fixed in 3.6.10.Final - org.jgroups:jgroups (Maven): affected from 3.3.0.Alpha1; fixed in 3.6.10.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-2141/ (Markdown: https://insights.sbomify.com/CVE-2016-2141/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2141 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2141 - OSV: https://osv.dev/vulnerability/CVE-2016-2141 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-2141/ Summaries are generated and may contain mistakes; the official description above is the record.