# CVE-2012-2377: Missing authorization in n/a

> Remote attackers on adjacent networks can read sensitive diagnostics information from JBoss platforms due to an unauthenticated JGroups service.

- **Severity:** Low 3.3 (`AV:A/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jm5c-rgfp-cjhx

## What is CVE-2012-2377?

CVE-2012-2377 is a low-severity missing authorization vulnerability in n/a, published on 23 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

JGroups diagnostics service in JBoss Enterprise Portal Platform before 5.2.2, SOA Platform before 5.3.0, and BRMS Platform before 5.3.0, is enabled without authentication when started by the JGroups channel, which allows remote attackers in adjacent networks to read diagnostics information via a crafted IP multicast.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-2377?

It affects 3 products.


Products: Redhat Jboss Enterprise Brms Platform, Redhat Jboss Enterprise Portal Platform, Redhat Jboss Enterprise Soa Platform.

## How do I fix CVE-2012-2377?

Upgrade to a fixed version.

## Is CVE-2012-2377 being exploited?

There is no known exploitation of CVE-2012-2377 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-2186](https://insights.sbomify.com/CVE-2013-2186/): Arbitrary file write in Apache Commons Fileupload (high 7.5)
- [CVE-2011-2908](https://insights.sbomify.com/CVE-2011-2908/): Cross-site request forgery in n/a (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2377 and fix it if it is affected.

What it is: CVE-2012-2377 is a low-severity missing authorization vulnerability in n/a, published on 23 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2377 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2012-2377/ (Markdown: https://insights.sbomify.com/CVE-2012-2377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2377
- OSV: https://osv.dev/vulnerability/CVE-2012-2377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2377/
Summaries are generated and may contain mistakes; the official description above is the record.