CVE-2013-4112: JGroup - Exposure of Sensitive Information to an Unauthorized Actor

org.jgroups:jgroups Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Moderate
Not published

CVE-2013-4112: Exposure of Sensitive Information to an Unauthorized Actor in JGroup. Affects org.jgroups:jgroups across 2 version ranges.

>= 3.0.0, < 3.2.9.Final >= 3.3.0, < 3.3.3.Final

Fixed in 3.2.9.Final or 3.3.3.Final, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2013-4112 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

JGroup is a library that provides reliable group communication for Java applications. It allows processes to join a group and communicate with each other using multicast or unicast communication. JGroup is widely used in distributed systems and provides features such as message ordering, reliability, and fault tolerance. However, versions 3.0.x, 3.1.x, 3.2.x before 3.2.9, and 3.3.x before 3.3.3 of JGroup are vulnerable to an exposure of sensitive information and arbitrary code execution.

Vulnerability Detail

The vulnerability, identified as CVE-2013-4112, exists in the DiagnosticsHandler component of JGroup. It allows remote attackers to obtain sensitive information, specifically diagnostic information, and execute arbitrary code by reusing valid credentials. This vulnerability can be exploited by unauthorized actors to gain unauthorized access to sensitive data and potentially compromise the entire system. It is important to note that this vulnerability has a moderate severity rating.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.2.9.Final 3.2.9.Final
  • >= 3.3.0, < 3.3.3.Final 3.3.3.Final

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general best practice, it is recommended to follow secure coding practices, such as implementing strong authentication mechanisms, regularly updating dependencies, and monitoring for any suspicious activity.

Conclusion

The vulnerability in JGroup (CVE-2013-4112) exposes sensitive information to unauthorized actors and allows arbitrary code execution. To mitigate this vulnerability, it is crucial to upgrade to a fixed version of JGroup (3.2.9.Final or 3.3.3.Final) and review/update authentication credentials. For further assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jgroups:jgroups →

Share this vulnerability

FAQ

JGroup is a Java library that provides reliable group communication for distributed systems.

The vulnerability allows unauthorized actors to access sensitive information and execute arbitrary code, potentially leading to unauthorized access and compromise of the system.

To fix this vulnerability, upgrade to a fixed version of JGroup (3.2.9.Final or 3.3.3.Final) and review/update any credentials used for authentication within the JGroup configuration.

There are no specific workarounds mentioned for this vulnerability. However, following secure coding practices and regularly updating dependencies can help mitigate the risk.

The vulnerability has a moderate severity rating.

Related vulnerabilities

Recent vulnerabilities recorded for org.jgroups:jgroups.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.2.9.Final 3.2.9.Final
  • >= 3.3.0, < 3.3.3.Final 3.3.3.Final

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback