dbcve.org
Jboss Enterprise Brms PlatformApplication · Redhat

CVE-2011-2908

MEDIUM · 6.0 CVSS v2.0 Published 2012-11-23
Fix available
A fix is available. Upgrade to after 5.2.1 or later.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CSRF vulnerability in JBoss JMX Console allows authenticated attackers to hijack other users' sessions and perform operations on MBeans, potentially leading to arbitrary code execution. The vulnerability affects JBoss Enterprise Portal Platform, BRMS Platform, and SOA Platform versions prior to the specified patches.

MitigationApply vendor patches (Portal Platform 5.2.2+, BRMS/SOA roll up patch1+) and restrict or disable JMX Console access if not required. Implement CSRF tokens if continued use is necessary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Brms PlatformApplication
Affected:= 5.3.0
Jboss Enterprise Portal PlatformApplication
Affected:<= 5.2.1= 5.0.0= 5.0.1= 5.1.0= 5.1.1= 5.2.0
Jboss Enterprise Soa PlatformApplication
Affected:= 5.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JBoss installation and version
    Locate the JBoss installation directory and check version files (such as version.properties, manifest files, or startup logs). Common paths include $JBOSS_HOME/bin/run.jar or check the application server's welcome page.
    Affected if The installed version matches Red Hat JBoss Enterprise BRMS Platform 5.3.0, Portal Platform versions 5.0.0 through 5.2.1 (including 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.2.0), or SOA Platform 5.3.0.
  2. Verify JMX Console is deployed and accessible
    Attempt to access the JMX Console web interface by navigating to the /jmx-console/ path on the server (for example, http://hostname:port/jmx-console/). Check if the deployment exists in $JBOSS_HOME/server/<profile>/deploy/jmx-console.war/
    Affected if The JMX Console is deployed and accessible without authentication requirements or the console responds successfully to HTTP requests.
  3. Inspect JMX Console configuration for CSRF protection
    Examine the JMX Console deployment descriptor (web.xml) located in $JBOSS_HOME/server/<profile>/deploy/jmx-console.war/WEB-INF/web.xml. Look for any CSRF filter, token validation, or referer checking servlet filters configured.
    Affected if The web.xml lacks CSRF protection mechanisms such as a security filter, token validation, or referer header checks.
  4. Check for custom CSRF countermeasures in application
    Review any custom filter or valve implementations in the JBoss server configuration (server.xml) or the JMX Console deployment descriptors that may implement CSRF token generation or session validation.
    Affected if No custom CSRF filters, valves, or token-based protections are found in the JMX Console or server configuration.

You are affected if you are running any of the specified JBoss Enterprise platform versions (BRMS 5.3.0, Portal Platform <= 5.2.1, or SOA Platform 5.3.0) with the JMX Console deployed and accessible, and the JMX Console lacks CSRF protection configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.2.1
Interim mitigation

Apply vendor patches (Portal Platform 5.2.2+, BRMS/SOA roll up patch1+) and restrict or disable JMX Console access if not required. Implement CSRF tokens if continued use is necessary.

Fix this in Jboss Enterprise Brms Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-2908 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data