The Vigil@nce team watches public vulnerabilities impacting your computers, and then offers security solutions, a database and tools to fix them.

Computer vulnerabilities of MuleSoft Mule Runtime

vulnerability note 16684

Mule ESB: Man-in-the-middle of HTTP Connector

Synthesis of the vulnerability

An attacker can act as a Man-in-the-middle on the HTTP Connector of Mule ESB, in order to capture or alter data.
Impacted products: Mule ESB.
Severity: 2/4.
Consequences: data reading, data creation/edition.
Provenance: intranet server.
Creation date: 21/04/2015.
Identifiers: VIGILANCE-VUL-16684.

Description of the vulnerability

The Mule ESB product uses the HTTP Connector to connect to web sites.

However, the HTTP Connector does not check the X.509 certificate.

An attacker can therefore act as a Man-in-the-middle on the HTTP Connector of Mule ESB, in order to capture or alter data.
Full Vigil@nce bulletin... (Free trial)

vulnerability 16270

OpenSAML Java: invalid trust by MetadataPKIX

Synthesis of the vulnerability

An attacker with a certificate provided by one of the Trust Anchors indicated in shibmd:KeyAuthority can impersonate the identity of an entity, in order to escalate his privileges on an application using OpenSAML Java.
Impacted products: Mule ESB, OpenSAML-J.
Severity: 3/4.
Consequences: user access/rights.
Provenance: user account.
Creation date: 26/02/2015.
Identifiers: VIGILANCE-VUL-16270.

Description of the vulnerability

The OpenSAML Java product uses the MetadataPKIX trust engine.

However, MetadataPKIX accepts an X.509 credential when there is no Trusted Name available for an entityID. This case occurs when an entity has a RoleDescriptor KeyDescriptor containing no KeyName element. Editor's announce indicates the list of vulnerable configurations.

An attacker with a certificate provided by one of the Trust Anchors indicated in shibmd:KeyAuthority can therefore impersonate the identity of an entity, in order to escalate his privileges on an application using OpenSAML Java.
Full Vigil@nce bulletin... (Free trial)

computer vulnerability announce 15527

Mulesoft Mule ESB: code execution

Synthesis of the vulnerability

An attacker can inject Java code into the management console of Mulesoft Mule ESB, in order to, for instance, raise his privileges.
Impacted products: Mule ESB.
Severity: 3/4.
Consequences: administrator access/rights, privileged access/rights.
Provenance: intranet client.
Creation date: 23/10/2014.
Revision date: 27/10/2014.
Identifiers: VIGILANCE-VUL-15527.

Description of the vulnerability

The Mulesoft ESB product include a web management console.

This service is used as an RPC server. However, it does not rightly checks the arguments of the call. So, an authenticated attacker can call unauthorized procedures. The attack example suggests that the service deserializes and run the HTTP body without sufficient restrictions about the request content.

An attacker can therefore inject Java code into Mulesoft Mule ESB, in order to, for instance, raise his privileges.
Full Vigil@nce bulletin... (Free trial)

computer vulnerability bulletin CVE-2014-0107

Xalan-Java: vulnerabilities of FEATURE_SECURE_PROCESSING

Synthesis of the vulnerability

An attacker can use several vulnerabilities of the FEATURE_SECURE_PROCESSING implementation in Xalan-Java.
Impacted products: Xalan-Java, Debian, Fedora, SiteScope, Mule ESB, openSUSE, RHEL, JBoss EAP by Red Hat, SUSE Linux Enterprise Desktop, SLES, Ubuntu.
Severity: 2/4.
Consequences: user access/rights, data reading.
Provenance: document.
Number of vulnerabilities in this bulletin: 3.
Creation date: 25/03/2014.
Identifiers: c05324755, CERTFR-2014-AVI-252, CERTFR-2014-AVI-365, CVE-2014-0107, DSA-2886-1, FEDORA-2014-4426, FEDORA-2014-4443, HPSBGN03669, oCERT-2014-002, openSUSE-SU-2014:0861-1, openSUSE-SU-2014:0948-1, RHSA-2014:0348-01, RHSA-2014:0453-01, RHSA-2014:0454-01, RHSA-2014:0590-01, RHSA-2014:0591-01, RHSA-2014:0818-01, RHSA-2014:0819-01, RHSA-2014:1007-01, RHSA-2014:1059-01, RHSA-2014:1290-01, RHSA-2014:1291-01, RHSA-2014:1351-01, RHSA-2014:1369-01, RHSA-2014:1995-01, RHSA-2015:1009, SUSE-SU-2014:0870-1, USN-2218-1, VIGILANCE-VUL-14468, XALANJ-2435.

Description of the vulnerability

The FEATURE_SECURE_PROCESSING (http://javax.xml.XMLConstants/feature/secure-processing) constant requires Xalan-Java to analyze XML files in a secure way, in order for example to block denial of service attacks. However, it is impacted by three vulnerabilities.

An attacker can access to XSLT 1.0 system-property(), in order to obtain sensitive information. [severity:2/4]

The xalan:content-handler and xalan:entities properties can be used to load a class or an external resource. [severity:2/4; XALANJ-2435]

If BSF (Bean Scripting Framework) is in the classpath, an attacker can open a JAR, in order to execute code. [severity:2/4]
Full Vigil@nce bulletin... (Free trial)
Our database contains other pages. You can request a free trial to read them.

Display information about MuleSoft Mule Runtime: