Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1112545 - (CVE-2014-3518) CVE-2014-3518 JBoss EAP/AS 5: Remote code execution via unauthenticated JMX/RMI connector
CVE-2014-3518 JBoss EAP/AS 5: Remote code execution via unauthenticated JMX/R...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20140716,repo...
: Security
Depends On: 1112618 1112619 1112620 1112622
Blocks: 1112637
  Show dependency tree / graph
 
Reported: 2014-06-24 03:40 EDT by Arun Babu Neelicattu
Modified: 2015-07-31 03:22 EDT (History)
20 users (show)

See Also:
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 01:34:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0887 normal SHIPPED_LIVE Important: JBoss Remoting security update 2014-07-16 05:18:39 EDT

  None (edit)
Description Arun Babu Neelicattu 2014-06-24 03:40:15 EDT 
A partial implementation of JMX remoting (JSR 160) via jmx-remoting.sar was made available, and enabled by default, in community releases of JBoss Application Server (WildFly) 5.x. This implementation, as identified by upstream (JBoss Remoting) does not implement security as defined in JSR 160. A remote attacker could use this to potentially execute arbitrary code. Red Hat Enterprise Application Platform 5.x is not affected by default; however, it can be susceptible to such an attack if JMX remoting is enabled by deploying jmx-remoting.sar as provided in documented examples.
Comment 2 Arun Babu Neelicattu 2014-06-24 04:18:59 EDT 
External References:

https://access.redhat.com/solutions/1120423
Comment 4 Martin Prpič 2014-07-08 04:48:41 EDT 
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
Comment 5 errata-xmlrpc 2014-07-16 00:38:23 EDT 
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
Comment 6 Arun Babu Neelicattu 2014-07-16 00:59:31 EDT 
Acknowledgements:

Red Hat would like to thank Harun ESUR of Sceptive for reporting this issue.
Comment 7 Arun Babu Neelicattu 2014-07-17 06:23:09 EDT 
Victims Record:

https://github.com/victims/victims-cve-db/blob/master/database/java/2014/3518.yaml
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.