RHSA-2014:0254: Important: activemq security update

Published Mar 5, 2014
·
Updated

Apache ActiveMQ provides a SOA infrastructure to connect processes acrossheterogeneous systems.A flaw was found in Apache Camel's parsing of the FILENAME header.A remote attacker able to submit messages to a Camel route, which wouldwrite the provided message to a file, could provide expression language(EL) expressions in the FILENAME header, which would be evaluated on theserver. This could lead to arbitrary remote code execution in the contextof the Camel server process. (CVE-2013-4330)It was found that the Apache Camel XSLT component allowed XSL stylesheetsto call external Java methods. A remote attacker able to submit messages toa Camel route could use this flaw to perform arbitrary remote codeexecution in the context of the Camel server process. (CVE-2014-0003)It was discovered that the Spring OXM wrapper did not expose any propertyfor disabling entity resolution when using the JAXB unmarshaller. A remoteattacker could use this flaw to conduct XML External Entity (XXE) attackson web sites, and read files in the context of the user running theapplication server. The patch for this flaw disables external entityprocessing by default, and provides a configuration directive to re-enableit. (CVE-2013-4152)The HawtJNI Library class wrote native libraries to a predictable file namein /tmp/ when the native libraries were bundled in a JAR file, and nocustom library path was specified. A local attacker could overwrite thesenative libraries with malicious versions during the window between whenHawtJNI writes them and when they are executed. (CVE-2013-2035)The CVE-2013-2035 issue was discovered by Florian Weimer of the Red HatProduct Security Team, and the CVE-2014-0003 issue was discovered by DavidJorm of the Red Hat Security Response Team.All users of Red Hat OpenShift Enterprise 1.2.7 are advised to upgrade tothis updated package, which corrects these issues.

Affected Software

2 affected componentsFixes available
redhat/activemq<5.9.0-4.redhat.610328.el6
5.9.0-4.redhat.610328.el6
redhat/activemq-client<5.9.0-4.redhat.610328.el6
5.9.0-4.redhat.610328.el6

Remediation

Event History

Mar 5, 2014
Advisory Published
12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2014:0254?

The severity of RHSA-2014:0254 is classified as important due to the potential for remote code execution.

2

How do I fix RHSA-2014:0254?

To fix RHSA-2014:0254, you should update to the affected packages version 5.9.0-4.redhat.610328.el6 or higher.

3

Which versions of Apache ActiveMQ are affected by RHSA-2014:0254?

Apache ActiveMQ versions prior to 5.9.0-4.redhat.610328.el6 are affected by RHSA-2014:0254.

4

Can RHSA-2014:0254 lead to a denial of service?

Yes, RHSA-2014:0254 can potentially be exploited to lead to a denial of service through crafted messages.

5

Who is impacted by RHSA-2014:0254?

Organizations using Apache ActiveMQ with vulnerable versions are impacted by RHSA-2014:0254.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203