Improper Certificate Validationorg.opensaml:opensaml provides tools to support developers working with the Security Assertion Markup Language (SAML).
Affected versions of this package are vulnerable to Improper Certificate Validation.
HttpResource and FileBackedHttpResource implementations in OpenSAML Java and Shibboleth IdP did not enable hostname verification when using TLS connections. Additionaly, OpenSAML Java makes use of Jakarta Commons HttpClient version 3.x, which does not perform verification of the server hostname against the server's X.508 certificate (CVE-2012-5783). This flaw can be exploited by a Man-in-the-middle (MITM) attack, where the attacker can spoof a valid certificate using a specially crafted subject.
How to fix Improper Certificate Validation? Upgrade org.opensaml:opensaml to version 2.6.2 or higher.
| |
Improper Certificate Validationorg.opensaml:opensaml
The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor.
| |
Improper Authenticationorg.opensaml:opensaml
Shibboleth OpenSAML library 2.4.x before 2.4.3 and 2.5.x before 2.5.1, and IdP before 2.3.2, allows remote attackers to forge messages and bypass authentication via an "XML Signature wrapping attack."
| |
Information Exposureorg.opensaml:opensaml provides tools to support developers working with the Security Assertion Markup Language (SAML).
Affected versions of this package are vulnerable to Information Exposure.
The (1) BasicParserPool, (2) StaticBasicParserPool, (3) XML Decrypter, and (4) SAML Decrypter set the expandEntityReferences property to true, which allows remote attackers to conduct XML external entity (XXE) attacks via a crafted XML DOCTYPE declaration.
How to fix Information Exposure? Upgrade org.opensaml:opensaml to version 2.6.1 or higher.
| |