Improper Certificate Validation in vt-ldap
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| edu.vt.middleware:vt-ldap Maven |
|
|
| edu.internet2.middleware:shibboleth-identityprovider Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| edu.vt.middleware:vt-ldap Maven |
|
|
| edu.internet2.middleware:shibboleth-identityprovider Maven |
|
|
DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
From the CVE record · redhat
DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly check whether an SSL server’s hostname matches a domain name in the certificate’s Common Name field. A man-in-the-middle attacker can spoof an SSL server using an arbitrary valid certificate. The input does not specify authentication or user-interaction requirements.
Engineers using Maven edu.vt.middleware:vt-ldap versions before 3.3.8 or edu.internet2.middleware:shibboleth-identityprovider versions before 2.4.2 should check their dependencies.