OpenLDAP up to 2.4.29 Search Request Parser memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in OpenLDAP. Affected by this vulnerability is an unknown functionality of the component Search Request Parser. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2012-1164. Furthermore, there is an exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in OpenLDAP (Directory Service Software) and classified as problematic. This issue affects some unknown processing of the component Search Request Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. The summary by CVE is:

slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned.

The weakness was shared 01/29/2012 by Mattias (Website). The advisory is shared at openldap.org. The identification of this vulnerability is CVE-2012-1164 since 02/14/2012. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.

The exploit is available at openldap.org. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 68559 (Oracle Linux 6 : openldap (ELSA-2012-0899)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Oracle Linux Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196125 (Ubuntu Security Notification for Openldap Vulnerabilities (USN-2622-1)).

Upgrading to version 2.4.30 eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (76521), Tenable (68559), SecurityFocus (BID 52404†), OSVDB (80086†) and Secunia (SA48372†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.9
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 68559
Nessus Name: Oracle Linux 6 : openldap (ELSA-2012-0899)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 881227
OpenVAS Name: CentOS Update for openldap CESA-2012:0899 centos6
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: OpenLDAP 2.4.30

Timelineinfo

01/29/2012 🔍
02/14/2012 +16 days 🔍
02/29/2012 +15 days 🔍
02/29/2012 +0 days 🔍
02/29/2012 +0 days 🔍
03/12/2012 +12 days 🔍
03/13/2012 +1 days 🔍
03/16/2012 +3 days 🔍
06/29/2012 +105 days 🔍
07/08/2012 +9 days 🔍
07/12/2013 +369 days 🔍
03/22/2021 +2810 days 🔍

Sourcesinfo

Advisory: openldap.org
Researcher: Mattias
Status: Not defined
Confirmation: 🔍

CVE: CVE-2012-1164 (🔍)
GCVE (CVE): GCVE-0-2012-1164
GCVE (VulDB): GCVE-100-4829

OVAL: 🔍

X-Force: 76521
SecurityFocus: 52404 - OpenLDAP LDAP Search Request Remote Denial of Service Vulnerability
Secunia: 48372 - OpenLDAP Attributes Only LDAP Search Denial of Service Vulnerability, Less Critical
OSVDB: 80086
Vulnerability Center: 35485 - Slapd in OpenLDAP before 2.4.30 Remote Denial of Service Vulnerability via an LDAP Search Query, High

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 03/16/2012 16:34
Updated: 03/22/2021 06:44
Changes: 03/16/2012 16:34 (77), 04/14/2017 13:55 (11), 03/22/2021 06:44 (3)
Complete: 🔍
Cache ID: 216:BFD:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!