Bug 1112545 (CVE-2014-3518)
| Summary: | CVE-2014-3518 JBoss EAP/AS 5: Remote code execution via unauthenticated JMX/RMI connector | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Arun Babu Neelicattu <aneelica> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | ahecox, aneelica, bdawidow, dimitris, djorm, fnasser, grocha, hfnukal, huwang, jawilson, jpallich, jrusnack, lgao, mweiler, myarboro, pavelp, security-response-team, theute, tkirby, weli |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
JBoss Application Server 5 and supported Red Hat JBoss 5.x products contain JBoss Remoting, which includes a partial implementation of the JMX remoting specification JSR 160. This implementation is provided in jmx-remoting.sar, which is deployed by default in unsupported community releases of JBoss Application Server 5.x. This implementation does not implement security as defined in JSR 160, and therefore does not apply any authentication or authorization constraints. A remote attacker could use this flaw to potentially execute arbitrary code on a vulnerable server. All of the supported Red Hat JBoss 5.x products are not affected by this issue in their default configuration. These products are only vulnerable if JMX remoting is enabled by manually deploying jmx-remoting.sar from the jboss-as/docs/examples directory. Unsupported community releases of JBoss Application Server 5.x are affected. All users of the standalone JBoss Remoting project are also affected.
For more information, see https://access.redhat.com/solutions/1120423
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-16 05:34:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1112618, 1112619, 1112620, 1112622 | ||
| Bug Blocks: | 1112637 | ||
|
Description
Arun Babu Neelicattu
2014-06-24 07:40:15 UTC
External References: https://access.redhat.com/solutions/1120423 IssueDescription: JBoss Application Server 5 and supported Red Hat JBoss 5.x products contain JBoss Remoting, which includes a partial implementation of the JMX remoting specification JSR 160. This implementation is provided in jmx-remoting.sar, which is deployed by default in unsupported community releases of JBoss Application Server 5.x. This implementation does not implement security as defined in JSR 160, and therefore does not apply any authentication or authorization constraints. A remote attacker could use this flaw to potentially execute arbitrary code on a vulnerable server. All of the supported Red Hat JBoss 5.x products are not affected by this issue in their default configuration. These products are only vulnerable if JMX remoting is enabled by manually deploying jmx-remoting.sar from the jboss-as/docs/examples directory. Unsupported community releases of JBoss Application Server 5.x are affected. All users of the standalone JBoss Remoting project are also affected. For more information, see https://access.redhat.com/solutions/1120423 This issue has been addressed in following products: Red Hat JBoss Enterprise Application Platform 5.2 Red Hat JBoss Enterprise BRMS Platform 5.3 Red Hat JBoss Portal 5.2 Red Hat JBoss SOA Platform 5.3 Via RHSA-2014:0887 https://rhn.redhat.com/errata/RHSA-2014-0887.html Acknowledgements: Red Hat would like to thank Harun ESUR of Sceptive for reporting this issue. |