Jboss Enterprise Application PlatformApplication · Redhat
CVE-2012-3370
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 · uneditedThe SecurityAssociation.getCredential method in JBoss Enterprise Application Platform (EAP) before 5.2.0, Web Platform (EWP) before 5.2.0, BRMS Platform before 5.3.1, and SOA Platform before 5.3.1 returns the credentials of the previous user when a security context is not provided, which allows remote attackers to gain privileges as other users.
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 confidenceThe SecurityAssociation.getCredential method in affected JBoss platforms returns the credentials of the previous user when no security context is provided, causing authentication state leakage between requests. An unauthenticated or low-privilege attacker can exploit this to inherit credentials from a prior authenticated session, enabling privilege escalation to other user accounts.
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 Application PlatformApplication
= 5.2.0
Jboss Enterprise Web PlatformApplication
= 5.2.0
Jboss Enterprise Brms PlatformApplication
<= 5.3.0CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify JBoss platform versionCheck the installed version of JBoss Enterprise Application Platform, Web Platform, or BRMS. This is typically found in the version.txt or manifest file in the JBoss installation directory, or via the admin console.Affected if The installed version is 5.2.0 (EAP/EWP) or 5.3.0 or earlier (BRMS)
-
Locate SecurityAssociation usage in application codeSearch Java source code and compiled classes for calls to the getCredential method on the SecurityAssociation class. Search patterns: 'SecurityAssociation.getCredential' or imports of 'org.jboss.security.SecurityAssociation'.Affected if The application code calls SecurityAssociation.getCredential without first verifying a security context exists
-
Review authentication configurationExamine the security domain configuration in login-config.xml or the equivalent security configuration file for the deployed applications. Verify whether the configuration properly establishes and validates security context for each request.Affected if The security configuration lacks explicit validation that a security context is present before credentials are accessed
-
Check for credential leakage between requestsPerform authenticated requests as different users in sequence without proper session cleanup. Observe whether credentials from the first user persist or leak into subsequent unauthenticated or differently-authenticated requests.Affected if Credentials from a previous authenticated session are returned or accessible when no current security context exists
You are affected if you run JBoss EAP/EWP 5.2.0 or JBoss BRMS 5.3.0 or earlier AND your application uses SecurityAssociation.getCredential without verifying a security context exists first.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade JBoss EAP, EWP, BRMS, and SOA platforms to versions 5.2.0 or higher (5.3.1 for BRMS/SOA). As a compensating control, implement application-layer validation to verify the security context is present before trusting credentials from SecurityAssociation.
Fix this in Jboss Enterprise Application Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3370 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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