# CVE-2011-2908: Cross-site request forgery in n/a

> Remote authenticated users can hijack sessions via CSRF in JBoss JMX Console to perform MBean operations and potentially execute code.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x3w9-v829-qphw

## What is CVE-2011-2908?

CVE-2011-2908 is a medium-severity vulnerability in n/a, published on 23 Nov 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the JMX Console (jmx-console) in JBoss Enterprise Portal Platform before 5.2.2, BRMS Platform 5.3.0 before roll up patch1, and SOA Platform 5.3.0 allows remote authenticated users to hijack the authentication of arbitrary users for requests that perform operations on MBeans and possibly execute arbitrary code via unspecified vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2011-2908?

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-2011-2908?

Upgrade to a fixed version.

## Is CVE-2011-2908 being exploited?

There is no known exploitation of CVE-2011-2908 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-2012-2377](https://insights.sbomify.com/CVE-2012-2377/): Missing authorization in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2908 and fix it if it is affected.

What it is: CVE-2011-2908 is a medium-severity vulnerability in n/a, published on 23 Nov 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-2908 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-2011-2908/ (Markdown: https://insights.sbomify.com/CVE-2011-2908/index.md)
```

## Sources

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

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