CVE-2012-2312 json
An Elevated Privileges issue exists in JBoss AS 7 Community Release due to the improper implementation in the security context propagation,…
published 2019-12-18 6 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2305
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-2312 updated cvss 3.3
7: Security Context Propagation - When re-using thread from thread pool, security context also gets re-used
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- JBoss AS 7 JBoss
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2012-2312
issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2012-2312
vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2012-2312
third-party-advisory
Sources
- CVE List CVE-2012-2312
- NVD CVE-2012-2312
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.