CVE-2012-0743
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 · uneditedIBM Tivoli Directory Server (TDS) 6.3 and earlier allows remote attackers to cause a denial of service (daemon crash) via a malformed LDAP paged search request.
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 · moderate confidenceIBM Tivoli Directory Server (TDS) versions 6.3 and earlier contain a vulnerability in the LDAP paged search functionality. Remote attackers can send specially crafted malformed LDAP paged search requests to trigger a daemon crash, resulting in denial of service.
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<= 6.3.0= 3.2.2= 4.1= 5.2.0= 6.0= 6.0.0= 6.0.0.7= 6.0.0.8= 6.0.0.69= 6.1.0= 6.1.0.45= 6.1.0.46CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM Tivoli Directory Server is installedLocate the TDS installation directory and check for the 'idssvr' or 'ldapux' process. Common paths: /opt/IBM/ldap, /opt/IBM/tds, or check with 'ps -ef | grep -i ibm' or 'ls -la /opt/IBM/'. On Windows, check Services for 'IBM Tivoli Directory Server'.Affected if IBM TDS binaries or processes are found on the system
-
Determine the installed TDS versionRun the version command specific to TDS. Common methods: 'idsversion' command from the bin directory, or check the product version file in the installation directory (e.g., /opt/IBM/ldap/version). On Windows, right-click the service and select Properties.Affected if The installed version matches any of these affected versions: 6.3.0 and earlier, 3.2.2, 4.1, 5.2.0, 6.0, 6.0.0, 6.0.0.7, 6.0.0.8, 6.0.0.69, 6.1.0, 6.1.0.45, or 6.1.0.46
-
Confirm LDAP paged search is enabledInspect the TDS configuration file (ibmslapd.conf or ibmslapd.conf) in the instance directory. Look for the 'allow paged search' directive or check via the administrative console (tdadmin). The feature is typically enabled by default in affected versions.Affected if LDAP paged search functionality is enabled in the configuration (this is the default state in vulnerable versions)
-
Check LDAP service is listeningRun 'netstat -an | grep 389' or 'netstat -an | grep 636' to verify the LDAP ports are open. Use 'ps' to confirm the LDAP server daemon (ibmdiradm, ibmslapd) is running.Affected if LDAP ports 389 or 636 are open and the TDS daemon is actively listening
The environment is affected if IBM Tivoli Directory Server is installed with a version matching 6.3.0 or any of the specific versions listed (3.2.2 through 6.1.0.46), and the LDAP service is running with paged search enabled.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade IBM Tivoli Directory Server to a version newer than 6.3, or apply any available patches. If immediate patching is not possible, restrict LDAP port exposure to trusted networks using firewall rules.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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