CVE-2014-0169 json
In JBoss EAP 6 a security domain is configured to use a cache that is shared between all applications that are in the security domain.
published 2020-01-02 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0222
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
In JBoss EAP 6 a security domain is configured to use a cache that is shared between all applications that are in the security domain. This could allow an authenticated user in one application to access protected resources in another application without proper authorization. Although this is an intended functionality, it was not clearly documented which can mislead users into thinking that a security domain cache is isolated to a single application.
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-2014-0169 updated cvss 4.0
EAP: cache is shared between all applications in a security domain
-
Red Hat JBoss Enterprise Application Platform 6 doc-Security_Guide doc-Security_Guideaffected: no fix available
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.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Red Hat JBoss EAP
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2014-0169
issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2014-0169
vendor-advisory
Sources
- CVE List CVE-2014-0169
- NVD CVE-2014-0169
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.