Red Hat JBoss Enterprise Application Platform (EAP) 6.1.0 does not properly cache EJB invocations by the EJB client API, which allows remote
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 84.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: jboss-as-client-all (Red Hat:jboss_enterprise_application_platform:6::el5) 0:7.2.0-9.Final_redhat_9.ep6.el5; jboss-ejb-client (Red Hat:jboss_enterprise_application_platform:6::el5) 0:1.0.21-2.Final_redhat_2.ep6.el5; jboss-remote-naming (Red Hat:jboss_enterprise_application_platform:6::el5) 0:1.0.6-3.Final_redhat_3.ep6.el5.
Low priority for now. Upgrade to jboss-as-client-all (Red Hat:jboss_enterprise_application_platform:6::el5) 0:7.2.0-9.Final_redhat_9.ep6.el5; jboss-ejb-client (Red Hat:jboss_enterprise_application_platform:6::el5) 0:1.0.21-2.Final_redhat_2.ep6.el5; jboss-remote-naming (Red Hat:jboss_enterprise_application_platform:6::el5) 0:1.0.6-3.Final_redhat_3.ep6.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Red Hat JBoss Enterprise Application Platform (EAP) 6.1.0 does not properly cache EJB invocations by the EJB client API, which allows remote attackers to hijack sessions by using an EJB client.
- Published
- Aug 16, 2013
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 85th percentile
- CWE
- CWE-284
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat jboss enterprise application platform6.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-client-all | before 0:7.2.0-9.Final_redhat_9.ep6.el5 | 0:7.2.0-9.Final_redhat_9.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-ejb-client | before 0:1.0.21-2.Final_redhat_2.ep6.el5 | 0:1.0.21-2.Final_redhat_2.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-remote-naming | before 0:1.0.6-3.Final_redhat_3.ep6.el5 | 0:1.0.6-3.Final_redhat_3.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | jboss-as-client-all | before 0:7.2.0-9.Final_redhat_9.ep6.el6 | 0:7.2.0-9.Final_redhat_9.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | jboss-ejb-client | before 0:1.0.21-2.Final_redhat_2.ep6.el6 | 0:1.0.21-2.Final_redhat_2.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | jboss-remote-naming | before 0:1.0.6-3.Final_redhat_3.ep6.el6 | 0:1.0.6-3.Final_redhat_3.ep6.el6 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-12149In Jboss Application Server as shipped with Red Hat Enterprise Application Platform 5.2, it was found that the doFilter method in the ReadOnKEV96Now
- CVE-2010-1871JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for KEV90Now
- CVE-2010-1428The Web Console (aka web-console) in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP09KEV78This week
- CVE-2010-0738The JMX-Console web application in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP09 aKEV75This week
- CVE-2016-2183The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of appr58Plan
- CVE-2017-7504HTTPServerILServlet.java in JMS over HTTP Invocation Layer of the JbossMQ implementation, which is enabled by default in Red Hat Jboss Appli51Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:jboss-as-client-all | 0:7.2.0-9.Final_redhat_9.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-ejb-client | 0:1.0.21-2.Final_redhat_2.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-remote-naming | 0:1.0.6-3.Final_redhat_3.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.