dbcve.org
Tivoli Directory ServerApplication · Ibm

CVE-2011-1206

HIGH · 10.0 CVSS v2.0 Published 2011-04-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in ibmslapd.exe (LDAP server daemon) in IBM Tivoli Directory Server allows remote attackers to execute arbitrary code via crafted LDAP requests. The vulnerability exists in the server process handling malformed LDAP queries.

MitigationApply vendor-supplied Interim Fixes (IF) for the specific TDS version in use (5.2.0.5-TIV-ITDS-IF0010, 6.0.0.67, 6.1.0.40, 6.2.0.16, or 6.3.0.3). If patching is delayed, restrict LDAP network access to trusted sources and enable LDAP request validation/filtering at network perimeter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tivoli Directory ServerApplication
Affected:= 5.2.0= 5.2.0.4= 6.0= 6.0.0.0= 6.0.0.1= 6.0.0.7= 6.0.0.8= 6.0.0.14= 6.0.0.19= 6.0.0.33= 6.0.0.41= 6.0.0.45

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IBM Tivoli Directory Server is installed
    Check for the presence of the ibmslapd.exe process or the TDS installation directory. On Windows, look in the installation path (commonly C:\IBM\TDS or C:\Program Files\IBM\TDS). On Unix/Linux, check /opt/ibm/ldap or similar paths. Use commands like 'tasklist | findstr ibmslapd' on Windows or 'ps -ef | grep ibmslapd' on Unix to find running instances.
    Affected if IBM Tivoli Directory Server is installed and the ibmslapd.exe process exists on the system
  2. Identify the installed TDS version
    Use the vendor-provided version identification method. On Windows, check the program version through the Windows Registry under HKLM\Software\IBM\Tivoli\Directory or inspect the ibmslapd.exe file properties. On Unix/Linux, run 'ldapsearch -V' or check the installed package version via the system package manager (e.g., 'rpm -q ibmtivolidi').
    Affected if The installed version matches one of these: 5.2.0, 5.2.0.4, 6.0, 6.0.0.0, 6.0.0.1, 6.0.0.7, 6.0.0.8, 6.0.0.14, 6.0.0.19, 6.0.0.33, 6.0.0.41, or 6.0.0.45
  3. Verify the LDAP server daemon is running and network-exposed
    Confirm that ibmslapd.exe is actively running and listening on LDAP ports (default 389 or 636 for LDAPS). On Windows, use 'netstat -ano | findstr :389' or the LDAP port in use. On Unix/Linux, run 'netstat -tlnp | grep -E "389|636"' or 'ss -tlnp | grep -E "389|636"'.
    Affected if The ibmslapd.exe process is running and bound to a network interface accessible to remote attackers (not localhost-only or firewalled)
  4. Check if Interim Fixes have been applied
    Query the installed fixes or patches. On Windows, check the TDS installation for applied Interim Fixes in the Fixes or patches directory. On Unix/Linux, review the installed iFixes via the installation history or by examining the itds_patch_version or similar metadata files in the installation directory.
    Affected if No vendor-supplied Interim Fixes (IF0010 for 5.2.0.x, or version 6.0.0.67/6.1.0.40/6.2.0.16/6.3.0.3 or later for 6.x versions) have been installed

A system is affected if IBM Tivoli Directory Server is installed with a version matching 5.2.0, 5.2.0.4, 6.0, or any 6.0.0.x version through 6.0.0.45, the ibmslapd LDAP daemon is running and network-accessible, and no vendor-supplied Interim Fixes have been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.ibm.com →
Interim mitigation

Apply vendor-supplied Interim Fixes (IF) for the specific TDS version in use (5.2.0.5-TIV-ITDS-IF0010, 6.0.0.67, 6.1.0.40, 6.2.0.16, or 6.3.0.3). If patching is delayed, restrict LDAP network access to trusted sources and enable LDAP request validation/filtering at network perimeter.

Recommended fix High confidence

Upgrade to the appropriate fixed version: TDS 5.2.0.5-TIV-ITDS-IF0010, 6.0.0.8-TIV-ITDS-IF0009, 6.1.0.5-TIV-ITDS-IF0003, 6.2.0.3-TIV-ITDS-IF0002, or 6.3.0.0-TIV-ITDS-IF0003 (or later)

  1. 1. Identify the currently installed IBM Tivoli Directory Server version by checking the ibmslapd.exe file version or using the 'idsversion' command
  2. 2. Based on your current version, download the appropriate interim fix (IF) from IBM Support: For TDS 5.2.x, apply 5.2.0.5-TIV-ITDS-IF0010; for TDS 6.0.x, apply 6.0.0.8-TIV-ITDS-IF0009; for TDS 6.1.x, apply 6.1.0.5-TIV-ITDS-IF0003; for TDS 6.2.x, apply 6.2.0.3-TIV-ITDS-IF0002; for TDS 6.3.x, apply 6.3.0.0-TIV-ITDS-IF0003
  3. 3. Stop the IBM Tivoli Directory Server (TDS) service before applying the patch
  4. 4. Backup the current TDS installation directory and configuration files
  5. 5. Apply the downloaded interim fix following IBM's installation instructions from the support document
  6. 6. Restart the TDS service after patch application
  7. 7. Verify the patch was applied successfully by checking the version shows the updated fix level
  8. 8. Test that LDAP functionality continues to work properly
Caveat Review IBM's fix documentation for any configuration changes required; test thoroughly in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tivoli Directory Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1206 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data