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.

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 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.

Alvaro Munoz discovered a XML External Entity (XXE) injection in the Spring Framework which can be used for conducting CSRF and DoS attacks on other sites.

The Spring OXM wrapper did not expose any property for disabling entity resolution when using the JAXB unmarshaller. There are four possible source implementations passed to the unmarshaller :

  - DOMSource
  - StAXSource

  - SAXSource

  - StreamSource

For a DOMSource, the XML has already been parsed by user code and that code is responsible for protecting against XXE.


For a StAXSource, the XMLStreamReader has already been created by user code and that code is responsible for protecting against XXE.

For SAXSource and StreamSource instances, Spring processed external entities by default thereby creating this vulnerability.

The issue was resolved by disabling external entity processing by default and adding an option to enable it for those users that need to use this feature when processing XML from a trusted source.

It was also identified that Spring MVC processed user provided XML with JAXB in combination with a StAX XMLInputFactory without disabling external entity resolution. External entity resolution has been disabled in this case.

ID	Name	Product	Family	Published	Updated	Severity
119346	RHEL 6 : activemq (RHSA-2014:0245)	Nessus	Red Hat Local Security Checks	12/4/2018	4/15/2025	high
311947	RHCOS 2 : activemq (RHSA-2014:0245)	Nessus	Red Hat Local Security Checks	5/4/2026	5/4/2026	high
119347	RHEL 6 : activemq (RHSA-2014:0254)	Nessus	Red Hat Local Security Checks	12/4/2018	7/17/2024	high
311976	RHCOS 1 : activemq (RHSA-2014:0254)	Nessus	Red Hat Local Security Checks	5/4/2026	5/4/2026	high
71933	Debian DSA-2842-1 : libspring-java - denial of service	Nessus	Debian Local Security Checks	1/14/2014	1/11/2021	medium

Detections

Analytics

Plugins Search

high

high

high

high

medium