ibm Tivoli Directory Server up to 6.0.0.32 ibmslapd.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ibm Tivoli Directory Server up to 6.0.0.32. Impacted is an unknown function of the file ibmslapd.exe. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2011-1206. Moreover, an exploit is present. You should upgrade the affected component.
Details
A vulnerability was found in ibm Tivoli Directory Server up to 6.0.0.32 (Directory Service Software) and classified as critical. This issue affects some unknown functionality of the file ibmslapd.exe. 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 confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow in the server process in ibmslapd.exe in IBM Tivoli Directory Server (TDS) 5.2 before 5.2.0.5-TIV-ITDS-IF0010, 6.0 before 6.0.0.67 (aka 6.0.0.8-TIV-ITDS-IF0009), 6.1 before 6.1.0.40 (aka 6.1.0.5-TIV-ITDS-IF0003), 6.2 before 6.2.0.16 (aka 6.2.0.3-TIV-ITDS-IF0002), and 6.3 before 6.3.0.3 (aka 6.3.0.0-TIV-ITDS-IF0003) allows remote attackers to execute arbitrary code via a crafted LDAP request. NOTE: some of these details are obtained from third party information.
The weakness was disclosed 04/21/2011 by Francis Provencher (Website). It is possible to read the advisory at ibm.com. The identification of this vulnerability is CVE-2011-1206. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
A public exploit has been developed by Francis Provencher and been published before and not just after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 53625 (IBM Tivoli Directory Server Vulnerabilities (credentialed check)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows. The commercial vulnerability scanner Qualys is able to test this issue with plugin 119448 (IBM Tivoli Directory Server SASL Bind Request Remote Code Execution Vulnerability).
Upgrading to version 6.0.0.33 eliminates this vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 11092.
The vulnerability is also documented in the databases at X-Force (66711), Exploit-DB (17188), Tenable (53625) and Vulnerability Center (SBV-31453†). The entries VDB-57228, VDB-57225, VDB-57224 and VDB-57223 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.0.0.0
- 6.0.0.1
- 6.0.0.2
- 6.0.0.3
- 6.0.0.4
- 6.0.0.5
- 6.0.0.6
- 6.0.0.7
- 6.0.0.8
- 6.0.0.9
- 6.0.0.10
- 6.0.0.11
- 6.0.0.12
- 6.0.0.13
- 6.0.0.14
- 6.0.0.15
- 6.0.0.16
- 6.0.0.17
- 6.0.0.18
- 6.0.0.19
- 6.0.0.20
- 6.0.0.21
- 6.0.0.22
- 6.0.0.23
- 6.0.0.24
- 6.0.0.25
- 6.0.0.26
- 6.0.0.27
- 6.0.0.28
- 6.0.0.29
- 6.0.0.30
- 6.0.0.31
- 6.0.0.32
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Francis Provencher
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 53625
Nessus Name: IBM Tivoli Directory Server Vulnerabilities (credentialed check)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 902507
OpenVAS Name: IBM Tivoli Directory Server SASL Bind Request Remote Code Execution Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Tivoli Directory Server 6.0.0.33
TippingPoint: 🔍
McAfee IPS: 🔍
McAfee IPS Version: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍
Timeline
03/03/2011 🔍04/19/2011 🔍
04/19/2011 🔍
04/21/2011 🔍
04/21/2011 🔍
04/21/2011 🔍
05/02/2011 🔍
05/15/2011 🔍
03/23/2015 🔍
01/15/2025 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Researcher: Francis Provencher
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2011-1206 (🔍)
GCVE (CVE): GCVE-0-2011-1206
GCVE (VulDB): GCVE-100-57227
X-Force: 66711
SecurityFocus: 47121
Secunia: 44184
Vulnerability Center: 31453 - IBM Tivoli Directory Server Remote Code Execution via a Crafted LDAP Request, Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 01/15/2025 20:21
Changes: 03/23/2015 16:50 (64), 03/22/2017 09:54 (16), 11/05/2021 08:12 (4), 11/05/2021 08:16 (2), 01/15/2025 20:21 (16)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.