CWE
79
Advisory Published

RHSA-2014:0401: Moderate: Red Hat JBoss A-MQ 6.1.0 update

First published: Mon Apr 14 2014(Updated: )

Red Hat JBoss A-MQ, based on Apache ActiveMQ, is a standards-compliant<br>messaging system that is tailored for use in mission critical applications.<br>Red Hat JBoss A-MQ 6.1.0 is a minor product release that updates Red Hat<br>JBoss A-MQ 6.0.0 and includes several bug fixes and enhancements. Refer to<br>the Release Notes document, available from the link in the References<br>section, for a list of changes.<br>The following security issues are resolved with this update:<br>A flaw was found in the Apache Hadoop RPC protocol. A man-in-the-middle<br>attacker could possibly use this flaw to unilaterally disable bidirectional<br>authentication between a client and a server, forcing a downgrade to simple<br>(unidirectional) authentication. This flaw only affected users who have<br>enabled Hadoop's Kerberos security features. (CVE-2013-2192)<br>It was discovered that the Spring OXM wrapper did not expose any property<br>for disabling entity resolution when using the JAXB unmarshaller. A remote<br>attacker could use this flaw to conduct XML External Entity (XXE) attacks<br>on web sites, and read files in the context of the user running the<br>application server. The patch for this flaw disables external entity<br>processing by default, and provides a configuration directive to re-enable<br>it. (CVE-2013-4152)<br>It was found that the Spring MVC SourceHttpMessageConverter enabled entity<br>resolution by default. A remote attacker could use this flaw to conduct XXE<br>attacks on web sites, and read files in the context of the user running the<br>application server. The patch for this flaw disables external entity<br>processing by default, and introduces a property to re-enable it.<br>(CVE-2013-6429)<br>The Spring JavaScript escape method insufficiently escaped some characters.<br>Applications using this method to escape user-supplied content, which would<br>be rendered in HTML5 documents, could be exposed to cross-site scripting<br>(XSS) flaws. (CVE-2013-6430)<br>A denial of service flaw was found in the way Apache Commons FileUpload<br>handled small-sized buffers used by MultipartStream. A remote attacker<br>could use this flaw to create a malformed Content-Type header for a<br>multipart request, causing Apache Commons FileUpload to enter an infinite<br>loop when processing such an incoming request. (CVE-2014-0050)<br>It was found that fixes for the CVE-2013-4152 and CVE-2013-6429 XXE issues<br>in Spring were incomplete. Spring MVC processed user-provided XML and<br>neither disabled XML external entities nor provided an option to disable<br>them, possibly allowing a remote attacker to conduct XXE attacks.<br>(CVE-2014-0054)<br>A cross-site scripting (XSS) flaw was found in the Spring Framework when<br>using Spring MVC. When the action was not specified in a Spring form, the<br>action field would be populated with the requested URI, allowing an<br>attacker to inject malicious content into the form. (CVE-2014-1904)<br>The HawtJNI Library class wrote native libraries to a predictable file name<br>in /tmp when the native libraries were bundled in a JAR file, and no custom<br>library path was specified. A local attacker could overwrite these native<br>libraries with malicious versions during the window between when HawtJNI<br>writes them and when they are executed. (CVE-2013-2035)<br>An information disclosure flaw was found in the way Apache Zookeeper stored<br>the password of an administrative user in the log files. A local user with<br>access to these log files could use the exposed sensitive information to<br>gain administrative access to an application using Apache Zookeeper.<br>(CVE-2014-0085)<br>The CVE-2013-6430 issue was discovered by Jon Passki of Coverity SRL and<br>Arun Neelicattu of the Red Hat Security Response Team, the CVE-2013-2035<br>issue was discovered by Florian Weimer of the Red Hat Product Security<br>Team, and the CVE-2014-0085 issue was discovered by Graeme Colman of<br>Red Hat.<br>All users of Red Hat JBoss A-MQ 6.0.0 as provided from the Red Hat Customer<br>Portal are advised to apply this update.

Affected SoftwareAffected VersionHow to fix

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of RHSA-2014:0401?

    The severity of RHSA-2014:0401 is classified as moderate.

  • How do I fix RHSA-2014:0401?

    To fix RHSA-2014:0401, update your Red Hat JBoss A-MQ to version 6.1.0 or later.

  • What issues does RHSA-2014:0401 address?

    RHSA-2014:0401 addresses several bug fixes and enhancements in Red Hat JBoss A-MQ 6.1.0.

  • Which version of Red Hat JBoss A-MQ is affected by RHSA-2014:0401?

    RHSA-2014:0401 affects Red Hat JBoss A-MQ 6.0.0 and earlier versions.

  • Is there a workaround for RHSA-2014:0401?

    There are no documented workarounds for RHSA-2014:0401; updating is the recommended action.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203