CVE-2014-0018: Red Hat JBoss Enterprise Application Platform (JBEAP) 6.2.0 and JBoss WildFly Application Server, when run under a security manager, do not…
Noroxi assessment
Priority: Monitor (action score 7/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: 0.35% (FIRST EPSS).
- Fixed version: hornetq (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.3.14-1.Final_redhat_1.1.ep6.el5; jacorb-jboss (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.3.2-13.redhat_6.1.ep6.el5; jboss-as-appclient (Red Hat:jboss_enterprise_application_platform:6::el5) 0:7.3.1-3.Final_redhat_3.1.ep6.el5.
Low priority for now. Upgrade to hornetq (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.3.14-1.Final_redhat_1.1.ep6.el5; jacorb-jboss (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.3.2-13.redhat_6.1.ep6.el5; jboss-as-appclient (Red Hat:jboss_enterprise_application_platform:6::el5) 0:7.3.1-3.Final_redhat_3.1.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 (JBEAP) 6.2.0 and JBoss WildFly Application Server, when run under a security manager, do not properly restrict access to the Modular Service Container (MSC) service registry, which allows local users to modify the server via a crafted deployment.
- Published
- Feb 14, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-264
Report tools
Action score
7
Low priority for now.
- CVSS
- 7 / 40 · 1.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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.
Is your version affected? Check itNoroxi 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 |
| redhat | jboss wildfly application server | cpe:2.3:a:redhat:jboss_wildfly_application_server |
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.2.0
- redhat jboss wildfly application serverall versions
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 | hornetq | before 0:2.3.14-1.Final_redhat_1.1.ep6.el5 | 0:2.3.14-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jacorb-jboss | before 0:2.3.2-13.redhat_6.1.ep6.el5 | 0:2.3.2-13.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-appclient | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-cli | before 0:7.3.1-4.Final_redhat_3.1.ep6.el5 | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-client-all | before 0:7.3.1-4.Final_redhat_3.1.ep6.el5 | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-clustering | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-cmp | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-configadmin | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-connector | before 0:7.3.1-4.Final_redhat_3.1.ep6.el5 | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-controller | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-controller-client | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-core-security | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-deployment-repository | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-deployment-scanner | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-domain-http | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-domain-management | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-ee | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-ee-deployment | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-ejb3 | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-embedded | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-host-controller | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-jacorb | before 0:7.3.1-3.Final_redhat_3.1.ep6.el5 | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-jaxr | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-jaxrs | before 0:7.3.1-2.Final_redhat_3.1.ep6.el5 | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 |
+96
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…KEV96Now
- 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…KEV76This week
Published before and after this one in the same product
- ← EarlierCVE-2013-2133Dec 6, 2013 · The EJB invocation handler implementation in Red Hat JBossWS, as used in JBoss Enterprise Application Platform (EAP) before 6.2.0, does not…23Monitor
- ← EarlierCVE-2012-3427Feb 2, 2014 · Jboss-eap: aws-ec2: jboss eap and aws ec2: information disclosure via incorrect directory permissions22Monitor
- Later →CVE-2014-0058Feb 26, 2014 · The security audit functionality in Red Hat JBoss Enterprise Application Platform (EAP) 6.x before 6.2.1 logs request parameters in…7Monitor
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:hornetq | 0:2.3.14-1.Final_redhat_1.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jacorb-jboss | 0:2.3.2-13.redhat_6.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-appclient | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-cli | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-client-all | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-clustering | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-cmp | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-configadmin | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-connector | 0:7.3.1-4.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-controller | 0:7.3.1-3.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jboss-as-controller-client | 0:7.3.1-2.Final_redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:jbossas-javadocs | 0:7.3.1-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:L/AC:M/Au:N/C:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.