How severe is CVE-2013-4112?

No CVSS score has been assigned to CVE-2013-4112 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4112?

CVE-2013-4112 affects the following packages: org.jgroups:jgroups (Maven), org.jgroups:jgroups (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4112?

Update org.jgroups:jgroups to 3.2.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4112 is resolved across your whole dependency graph.

How do I detect CVE-2013-4112 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jgroups:jgroups, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4112 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-4112 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4112 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4112?

CVE-2013-4112 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4112?

CVE-2013-4112 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-4112 published, and has it been updated?

CVE-2013-4112 was published on September 28, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-4112 — jgroups

CVE-2013-4112 is a Information Exposure vulnerability in org.jgroups:jgroups. A fix is available for org.jgroups:jgroups — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in JGroup

Also known asGHSA-cc62-496p-hrr7

Published

Sep 28, 2013

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.jgroups:jgroups☕org.jgroups:jgroups

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The DiagnosticsHandler in JGroup 3.0.x, 3.1.x, 3.2.x before 3.2.9, and 3.3.x before 3.3.3 allows remote attackers to obtain sensitive information (diagnostic information) and execute arbitrary code by reusing valid credentials.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jgroups:jgroups`	≥ 3.0.0&&< 3.2.9.Final	3.2.9.Final`org.jgroups:jgroups:3.2.9.Final`
☕Maven	`org.jgroups:jgroups`	≥ 3.3.0&&< 3.3.3.Final	3.3.3.Final`org.jgroups:jgroups:3.3.3.Final`

Affected Products

2 products · 29 configurations

Application

jgroupjgroups

28 versions

3.0.03.0.13.0.23.0.33.0.43.0.53.0.63.0.73.0.83.0.93.0.103.0.11

Application

jboss enterprise application platformredhat

1 version

6.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jgroups:jgroups, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jgroups:jgroups to 3.2.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4112 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat JBoss Data Grid 6.2	`jgroups`	RHSA-2014:0029
Red Hat JBoss Enterprise Application Platform 6.1	`jgroups`	RHSA-2013:1209
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5	`apache-commons-beanutils-0:1.8.3-12.redhat_3.2.ep6.el5`	RHSA-2013:1207
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6	`apache-commons-beanutils-0:1.8.3-12.redhat_3.2.ep6.el6`	RHSA-2013:1208
Red Hat JBoss Portal Platform 6.1	`jgroups`	RHSA-2013:1437
Red Hat JBoss Web Framework Kit 2.4	`jgroups`	RHSA-2013:1771

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4112 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works