Skip to content
Fencer Intel
medium 5.0

CVE-2012-3429 json

The dns_to_ldap_dn_escape function in src/ldap_convert.c in bind-dyndb-ldap 1.1.0rc1 and earlier does not properly escape distinguished nam…

published 2012-08-07 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3396

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

The dns_to_ldap_dn_escape function in src/ldap_convert.c in bind-dyndb-ldap 1.1.0rc1 and earlier does not properly escape distinguished names (DN) for LDAP queries, which allows remote DNS servers to cause a denial of service (named service hang) via a "$" character in a DN in a DNS query.

Patch / fix

  • bind-dyndb-ldap RHEL 6 1.1.0-0.9.b1.el6_3.1

red hat advisories RHSA-2012:1139

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-3429 updated cvss 4.3

bind-dyndb-ldap: named DoS via DNS query with $ in name

  • Red Hat Enterprise Linux Server (v. 6) bind-dyndb-ldap 1.1.0-0.9.b1.el6_3.1 Red Hat Enterprise Linux Workstation (v. 6) bind-dyndb-ldap 1.1.0-0.9.b1.el6_3.1
    fixed: vendor fix RHSA-2012:1139

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.07% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • git.fedorahosted.org http://git.fedorahosted.org/cgit/bind-dyndb-ldap.git/commit/?id=f345805c73c294db42452ae966c48fbc36c48006 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.