CVE-2012-0726
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 · uneditedThe default configuration of TLS in IBM Tivoli Directory Server (TDS) 6.3 and earlier supports the (1) NULL-MD5 and (2) NULL-SHA ciphers, which allows remote attackers to trigger unencrypted communication via the TLS Handshake Protocol.
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 confidenceIBM Tivoli Directory Server (TDS) 6.3 and earlier has a default TLS configuration that enables NULL-MD5 and NULL-SHA cipher suites, which provide no encryption. Remote attackers can manipulate the TLS handshake protocol to force the use of these null ciphers, causing communication to occur in cleartext.
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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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.
-
Identify the installed IBM Tivoli Directory Server versionUse the command 'db2pd -db <dbname>' or check the IBM TDS installation directory for version information, or query the server via LDAP with version extended operationAffected if The installed version matches one of the affected versions: 6.3.0 and earlier, or specifically 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
-
Locate the TLS configuration for IBM Tivoli Directory ServerCheck the IBM TDS configuration files, typically in the installation directory under 'etc' or 'conf', or access the LDAP server configuration via the administrative console or command-line tools like 'idsldapsearch'Affected if A TLS or SSL configuration file exists and is in use by the server
-
Examine enabled cipher suites in the TLS configurationOpen the TLS/SSL configuration file and search for the 'ciphers' or 'sslCipherSpec' parameter, or use an administrative command to list configured cipher suitesAffected if The cipher configuration contains 'NULL-MD5' or 'NULL-SHA' (or 'NULL' ciphers) indicating these weak/no-encryption suites are enabled
-
Verify cipher suite order and priorityReview the cipher suite list in the TLS configuration to confirm whether NULL ciphers are listed and potentially selected during handshake negotiationAffected if NULL-MD5 or NULL-SHA ciphers are listed and could be selected during a TLS handshake with a remote client or server
A defender is affected if they run an affected IBM Tivoli Directory Server version AND have NULL-MD5 or NULL-SHA cipher suites enabled in their TLS configuration, allowing unencrypted communication to be forced by an attacker.
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 dataDisable NULL-MD5 and NULL-SHA cipher suites in the TLS configuration and configure only strong cipher suites (e.g., AES, 3DES) for encrypted communications.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0726 — 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-0726 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