CVE-2009-3767: libraries/libldap/tls_o.c in OpenLDAP 2.2 and 2.4, and possibly other versions, when OpenSSL is used, does...

Security readout for executives and security teams

OpenLDAP clients using OpenSSL could be tricked by a malicious certificate containing a null character in the Common Name. In a man-in-the-middle position, an attacker could make one SSL server appear to be another. The business risk is credential or directory-traffic interception where vulnerable LDAP/TLS clients remain unpatched. Exposure is most likely on legacy systems or products still using affected OpenLDAP libldap versions with OpenSSL for LDAPS or StartTLS. Modern fully patched distributions are less likely exposed, but embedded appliances and unsupported servers need explicit inventory checks. Treat as a legacy exposure cleanup item with high impact where vulnerable LDAP/TLS clients remain. It is not supported as actively exploited by the provided sources, but directory authentication traffic makes lingering instances important to remove. Mitigation focus: Apply vendor OpenLDAP updates or supported distribution backports.; Prioritize systems using LDAPS or StartTLS for authentication paths.; Replace unsupported OpenLDAP builds with maintained packages..

Prepared

Jun 28, 2026, 18:15 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.