CVE-2026-35563
highPriorität · verfolgen · 34EPSS 0.003 · 17. PerzentilEUUSEPSS · bewertet 2026-10-22
It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise. The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation. The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store. The hostname verification has been enforced in the new version of the LDAP API
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 5.9–8.8
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (3)
Betroffene Produkte und Versionsbereiche.
- Maven org.apache.directory.api:api-ldap-client-api2.0.0 → 2.1.8osvUSpkg:maven/org.apache.directory.api/api-ldap-client-api
Advisories (1)
Hersteller- und Ökosystem-Meldungen dazu.
- GHSA-85rw-g4f4-jprrApache Directory LDAP API lacks server certificate verification for LDAP hostnames2026-06-01ghsa · osvUS
It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise. The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation. The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store. The hostname verification has been enforced in the new version of the LDAP API.
auch bekannt als (3)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (6)
Externe Belege — Patches, Meldungen, Analysen.
- http://www.openwall.com/lists/oss-security/2026/06/01/2cnnvd
- https://access.redhat.com/security/cve/cve-2026-35563cnnvd
- https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nncnnvd
- https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nnenisa_euvd
- http://www.openwall.com/lists/oss-security/2026/06/01/2Mailing ListThird Party Advisorynvd
- https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nnMailing ListVendor Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan