dbcve.org
Jboss Application ServerApplication · Redhat

CVE-2012-2312

HIGH · 7.8 CVSS v3.1 Published 2019-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
An Elevated Privileges issue exists in JBoss AS 7 Community Release due to the improper implementation in the security context propagation, A threat gets reused from the thread pool that still retains the security context from the process last used, which lets a local user obtain elevated privileges.

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 · moderate confidence

JBoss AS 7 Community Release has a security context propagation flaw where threads reused from the thread pool retain the security context from their previous execution. This allows a local authenticated user to potentially inherit elevated privileges from a previously executed process using the same thread.

MitigationUpgrade to a patched version of JBoss AS 7 that properly clears security context when recycling threads, or implement proper thread pool security context isolation configurations.

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 Application ServerApplication
Affected:= 7.1.0= 7.1.1
Jboss Enterprise Application PlatformApplication
Affected:= 6.0.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 installed JBoss version
    Locate the version file: For JBoss AS 7, check $JBOSS_HOME/jboss-as-server/main/build/target or look for version.info or manifest.mf in the installation directories. For JBoss EAP 6, check $JBOSS_HOME/jboss-eap-6.x/modules/system/layers/base/.galaxy杉木.info or run the startup script with --version. The version is typically displayed at startup or in product-info.txt
    Affected if The installed version is exactly 7.1.0, 7.1.1 (JBoss AS 7 Community), or 6.0.0 (JBoss EAP)
  2. Verify JBoss product type
    Confirm whether the installation is JBoss Application Server (Community) or JBoss Enterprise Application Platform (EAP). Check the product name in the startup banner or in $JBOSS_HOME/product.conf or equivalent configuration file that defines the product name
    Affected if The product is JBoss AS 7.1.0 or 7.1.1 Community Edition, or JBoss EAP 6.0.0
  3. Check for thread pool configuration
    Examine the thread pool configuration in standalone.xml or domain.xml under the <threads> subsystem. Look for <thread-pool> elements in the Remoting, EJB, or other subsystem configurations. Check if custom thread pools are configured that could amplify the context retention issue
    Affected if Custom thread pools are configured with long-running threads or high thread counts that increase the likelihood of thread reuse with retained security context
  4. Assess security context usage
    Review application deployments and security configurations to determine if the server runs code with elevated privileges (such as run-as roles, security domains with privileged actions, or JACC permissions). Check standalone.xml for <security> subsystem configurations
    Affected if Security domains with elevated privileges or run-as principals are configured and the application performs privileged operations

A system is affected if it runs JBoss AS 7.1.0, 7.1.1, or JBoss EAP 6.0.0 and executes security-sensitive operations using threads that may be reused from the pool, allowing a local authenticated user to inherit elevated privileges from previously executed process contexts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of JBoss AS 7 that properly clears security context when recycling threads, or implement proper thread pool security context isolation configurations.

Fix this in Jboss Application Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2312 — 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-2012-2312 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