Race condition in hawtjni-runtime/src/main/java/org/fusesource/hawtjni/runtime/Library.java in HawtJNI before 1.8, when a custom library path is not specified, allows local users to execute arbitrary Java code by overwriting a temporary JAR file with a predictable name in /tmp.

The remote Red Hat Enterprise Linux CoreOS 1 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0254 advisory.

  - HawtJNI: predictable temporary file name leading to local arbitrary code execution (CVE-2013-2035)

  - Framework: XML External Entity (XXE) injection flaw (CVE-2013-4152)

  - Camel: remote code execution via header field manipulation (CVE-2013-4330)

  - Camel: remote code execution via XSL (CVE-2014-0003)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 2 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0245 advisory.

  - HawtJNI: predictable temporary file name leading to local arbitrary code execution (CVE-2013-2035)

  - Framework: XML External Entity (XXE) injection flaw (CVE-2013-4152)

  - Camel: remote code execution via header field manipulation (CVE-2013-4330)

  - Camel: remote code execution via XSL (CVE-2014-0003)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An updated activemq package that fixes multiple security issues is now available for Red Hat OpenShift Enterprise 1.2.7.

The Red Hat Security Response Team has rated this update as having Important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Apache ActiveMQ provides a SOA infrastructure to connect processes across heterogeneous systems.

A flaw was found in Apache Camel's parsing of the FILE_NAME header. A remote attacker able to submit messages to a Camel route, which would write the provided message to a file, could provide expression language (EL) expressions in the FILE_NAME header, which would be evaluated on the server. This could lead to arbitrary remote code execution in the context of the Camel server process. (CVE-2013-4330)

It was found that the Apache Camel XSLT component allowed XSL stylesheets to call external Java methods. A remote attacker able to submit messages to a Camel route could use this flaw to perform arbitrary remote code execution in the context of the Camel server process. (CVE-2014-0003)

It was discovered that the Spring OXM wrapper did not expose any property for disabling entity resolution when using the JAXB unmarshaller. A remote attacker could use this flaw to conduct XML External Entity (XXE) attacks on websites, and read files in the context of the user running the application server. The patch for this flaw disables external entity processing by default, and provides a configuration directive to re-enable it. (CVE-2013-4152)

The HawtJNI Library class wrote native libraries to a predictable file name in /tmp/ when the native libraries were bundled in a JAR file, and no custom library path was specified. A local attacker could overwrite these native libraries with malicious versions during the window between when HawtJNI writes them and when they are executed.
(CVE-2013-2035)

The CVE-2013-2035 issue was discovered by Florian Weimer of the Red Hat Product Security Team, and the CVE-2014-0003 issue was discovered by David Jorm of the Red Hat Security Response Team.

All users of Red Hat OpenShift Enterprise 1.2.7 are advised to upgrade to this updated package, which corrects these issues.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0245 advisory.

    Apache ActiveMQ provides a SOA infrastructure to connect processes across     heterogeneous systems.

    A flaw was found in Apache Camel's parsing of the FILE_NAME header.
    A remote attacker able to submit messages to a Camel route, which would     write the provided message to a file, could provide expression language     (EL) expressions in the FILE_NAME header, which would be evaluated on the     server. This could lead to arbitrary remote code execution in the context     of the Camel server process. (CVE-2013-4330)

    It was found that the Apache Camel XSLT component allowed XSL stylesheets     to call external Java methods. A remote attacker able to submit messages to     a Camel route could use this flaw to perform arbitrary remote code     execution in the context of the Camel server process. (CVE-2014-0003)

    It was discovered that the Spring OXM wrapper did not expose any property     for disabling entity resolution when using the JAXB unmarshaller. A remote     attacker could use this flaw to conduct XML External Entity (XXE) attacks     on web sites, and read files in the context of the user running the     application server. The patch for this flaw disables external entity     processing by default, and provides a configuration directive to re-enable     it. (CVE-2013-4152)

    The HawtJNI Library class wrote native libraries to a predictable file name     in /tmp/ when the native libraries were bundled in a JAR file, and no     custom library path was specified. A local attacker could overwrite these     native libraries with malicious versions during the window between when     HawtJNI writes them and when they are executed. (CVE-2013-2035)

    The CVE-2013-2035 issue was discovered by Florian Weimer of the Red Hat     Product Security Team, and the CVE-2014-0003 issue was discovered by David     Jorm of the Red Hat Security Response Team.

    All users of Red Hat OpenShift Enterprise 2.0 are advised to upgrade to     this updated package, which corrects these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update for Red Hat JBoss Enterprise Application Platform 6.2.0, which fixes two security issues, several bugs, and adds various enhancements, is now available from the Red Hat Customer Portal.

The Red Hat Security Response Team has rated this update as having low security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Red Hat JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7.

The HawtJNI Library class wrote native libraries to a predictable file name in /tmp/ when the native libraries were bundled in a JAR file, and no custom library path was specified. A local attacker could overwrite these native libraries with malicious versions during the window between when HawtJNI writes them and when they are executed.
(CVE-2013-2035)

A flaw was found in the way method-level authorization for JAX-WS Service endpoints was performed by the EJB invocation handler implementation. Any restrictions declared on EJB methods were ignored when executing the JAX-WS handlers, and only class-level restrictions were applied. A remote attacker who is authorized to access the EJB class, could invoke a JAX-WS handler which they were not authorized to invoke. (CVE-2013-2133)

The CVE-2013-2035 issue was discovered by Florian Weimer of the Red Hat Product Security Team, and the CVE-2013-2133 issue was discovered by Richard Opalka and Arun Neelicattu of Red Hat.

This release serves as a replacement for JBoss Enterprise Application Platform 6.1.1, and includes bug fixes and enhancements. Documentation for these changes will be available shortly from the JBoss Enterprise Application Platform 6.2.0 Release Notes, linked to in the References.

All users of Red Hat JBoss Enterprise Application Platform 6.2.0 as provided from the Red Hat Customer Portal are advised to apply this update. The JBoss server process must be restarted for the update to take effect.

This plugin does not check for JBoss installs on the following remote filesystem types: NFS, AFS, SMBFS, CIFS.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2013:1786 advisory.

    Red Hat JBoss Enterprise Application Platform 6 is a platform for Java     applications based on JBoss Application Server 7.

    The HawtJNI Library class wrote native libraries to a predictable file name     in /tmp/ when the native libraries were bundled in a JAR file, and no     custom library path was specified. A local attacker could overwrite these     native libraries with malicious versions during the window between when     HawtJNI writes them and when they are executed. (CVE-2013-2035)

    A flaw was found in the way method-level authorization for JAX-WS Service     endpoints was performed by the EJB invocation handler implementation.
    Any restrictions declared on EJB methods were ignored when executing the     JAX-WS handlers, and only class-level restrictions were applied. A remote     attacker who is authorized to access the EJB class, could invoke a JAX-WS     handler which they were not authorized to invoke. (CVE-2013-2133)

    The CVE-2013-2035 issue was discovered by Florian Weimer of the Red Hat     Product Security Team, and the CVE-2013-2133 issue was discovered by     Richard Opalka and Arun Neelicattu of Red Hat.

    This release serves as a replacement for JBoss Enterprise Application     Platform 6.1.1, and includes bug fixes and enhancements. Documentation for     these changes will be available shortly from the JBoss Enterprise     Application Platform 6.2.0 Release Notes, linked to in the References.

    All users of JBoss Enterprise Application Platform 6.1.1 on Red Hat     Enterprise Linux 6 are advised to upgrade to these updated packages. The     JBoss server process must be restarted for the update to take effect.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 5 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2013:1785 advisory.

    Red Hat JBoss Enterprise Application Platform 6 is a platform for Java     applications based on JBoss Application Server 7.

    The HawtJNI Library class wrote native libraries to a predictable file name     in /tmp/ when the native libraries were bundled in a JAR file, and no     custom library path was specified. A local attacker could overwrite these     native libraries with malicious versions during the window between when     HawtJNI writes them and when they are executed. (CVE-2013-2035)

    A flaw was found in the way method-level authorization for JAX-WS Service     endpoints was performed by the EJB invocation handler implementation.
    Any restrictions declared on EJB methods were ignored when executing the     JAX-WS handlers, and only class-level restrictions were applied. A remote     attacker who is authorized to access the EJB class, could invoke a JAX-WS     handler which they were not authorized to invoke. (CVE-2013-2133)

    The CVE-2013-2035 issue was discovered by Florian Weimer of the Red Hat     Product Security Team, and the CVE-2013-2133 issue was discovered by     Richard Opalka and Arun Neelicattu of Red Hat.

    This release serves as a replacement for JBoss Enterprise Application     Platform 6.1.1, and includes bug fixes and enhancements. Documentation for     these changes will be available shortly from the JBoss Enterprise     Application Platform 6.2.0 Release Notes, linked to in the References.

    All users of JBoss Enterprise Application Platform 6.1.1 on Red Hat     Enterprise Linux 5 are advised to upgrade to these updated packages.
    The JBoss server process must be restarted for the update to take effect.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
311976	RHCOS 1 : activemq (RHSA-2014:0254)	Nessus	Red Hat Local Security Checks	high
311947	RHCOS 2 : activemq (RHSA-2014:0245)	Nessus	Red Hat Local Security Checks	high
119347	RHEL 6 : activemq (RHSA-2014:0254)	Nessus	Red Hat Local Security Checks	high
119346	RHEL 6 : activemq (RHSA-2014:0245)	Nessus	Red Hat Local Security Checks	high
71900	RHEL 5 : JBoss EAP (RHSA-2013:1784)	Nessus	Red Hat Local Security Checks	medium
71225	RHEL 6 : Red Hat JBoss Enterprise Application Platform 6.2.0 update (Low) (RHSA-2013:1786)	Nessus	Red Hat Local Security Checks	medium
71224	RHEL 5 : Red Hat JBoss Enterprise Application Platform 6.2.0 update (Low) (RHSA-2013:1785)	Nessus	Red Hat Local Security Checks	medium

Detections

Analytics

CVE-2013-2035

medium

Tenable Plugins

high

high

high

high

medium

medium

medium