CVE-2012-3429: The dns_to_ldap_dn_escape function in src/ldap_convert.c in bind-dyndb-ldap 1.1.0rc1 and earlier does not p...

Security readout for executives and security teams

This flaw can make a DNS service using bind-dyndb-ldap hang when it processes a specially formed DNS query involving an LDAP distinguished name. The business impact is availability: affected DNS infrastructure may stop responding until recovered. The source bundle does not provide CVSS scoring or evidence of active exploitation. Exposure appears limited to DNS servers using bind-dyndb-ldap 1.1.0rc1 or earlier. Generic BIND deployments are not shown as affected unless this LDAP dynamic backend is installed and active. Prioritize if LDAP-backed DNS is still in production, because DNS availability is business-critical. For environments without bind-dyndb-ldap, this should be a low-effort inventory confirmation rather than an emergency response. Mitigation focus: Identify systems running bind-dyndb-ldap and their installed versions.; Apply vendor updates referenced by RHSA-2012:1139 or current distribution guidance.; Retire or isolate unsupported bind-dyndb-ldap 1.1.0rc1 and earlier deployments..

Prepared

Jun 27, 2026, 17:28 UTC (UTC+00:00)

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