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 OpenSAML Java

computer vulnerability bulletin CVE-2014-3603

OpenSAML Java: incomplete certificate validation

Synthesis of the vulnerability

An attacker can use any valid certificate on a malicious server, and then invite an Apache HttpClient 3 to connect there, in order to spy communications even if encryption is used.
Impacted products: Fedora, Mule ESB, OpenSAML-J.
Severity: 2/4.
Consequences: data reading, data creation/edition.
Provenance: internet server.
Creation date: 07/08/2015.
Identifiers: CVE-2014-3603, FEDORA-2015-10175, FEDORA-2015-10235, VIGILANCE-VUL-17608.

Description of the vulnerability

The OpenSAML Java library can manage HTTP connections over SSL, using Apache HttpClient 3 (VIGILANCE-VUL-12182).

In order to authenticate a server, the client must check the certificate (cryptographic signatures, validity date range, etc.) and also that the received certificate matches the visited server. This check is usually done on DNS names, or sometimes on IP addresses. However, HttpClient does not check that the names included in the certificates match the one requested at HTTP level. So, any valid certificate is accepted.

An attacker can therefore use any valid certificate on a malicious server, and then invite an OpenSAML Java to connect there, in order to spy communications even if encryption is used.
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 bulletin CVE-2014-3607

OpenSAML Java: incomplete certificate validation

Synthesis of the vulnerability

An attacker can use any valid certificate on a malicious server, and then invite an OpenSAML Java to connect there, in order to spy communications even if encryption is used.
Impacted products: OpenSAML-J.
Severity: 2/4.
Consequences: data reading.
Provenance: internet server.
Creation date: 22/09/2014.
Identifiers: CVE-2014-3607, VIGILANCE-VUL-15388.

Description of the vulnerability

The OpenSAML Java product can manage HTTP or LDAP connections over SSL.

In order to authenticate a server, the client must check the certificate (cryptographic signatures, validity date range, etc.) and also that the received certificate matches the visited server. This check is usually done on DNS names, or sometimes on IP addresses. However, OpenSAML Java does not check that the names included in the certificates match the one requested at HTTP level. So, any valid certificate is accepted.

An attacker can therefore use any valid certificate on a malicious server, and then invite an OpenSAML Java to connect there, in order to spy communications even if encryption is used.
Full Vigil@nce bulletin... (Free trial)
Our database contains other pages. You can request a free trial to read them.

Display information about OpenSAML Java: