What is the CVSS score of CVE-2012-2134?

CVE-2012-2134 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 1.0%.

Is there a patch available for CVE-2012-2134?

Yes, a patch is available for CVE-2012-2134. Update the affected software to the latest version immediately.

Bind Dyndb Ldap CVE-2012-2134

MEDIUM

Resource Management Errors (CWE-399)

2014-02-26 secalert@redhat.com

Denial Of Service Bind Dyndb Ldap

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:M/Au:N/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:N/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Feb 26, 2014 - 15:55 cve.org

MEDIUM 4.3

DescriptionCVE.org

The handle_connection_error function in ldap_helper.c in bind-dyndb-ldap before 1.1.0rc1 does not properly handle LDAP query errors, which allows remote attackers to cause a denial of service (infinite loop and named server hang) via a non-alphabet character in the base DN in an LDAP search DNS query.

AnalysisAI

The handle_connection_error function in ldap_helper.c in bind-dyndb-ldap before 1.1.0rc1 does not properly handle LDAP query errors, which allows remote attackers to cause a denial of service. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified under CWE-399. The handle_connection_error function in ldap_helper.c in bind-dyndb-ldap before 1.1.0rc1 does not properly handle LDAP query errors, which allows remote attackers to cause a denial of service (infinite loop and named server hang) via a non-alphabet character in the base DN in an LDAP search DNS query. Affected products include: Martin Nagy Bind-Dyndb-Ldap. Version information: before 1.1.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.