CVE-2005-3567 json
slapd daemon in IBM Tivoli Directory Server (ITDS) 5.2.0 and 6.0.0 binds using SASL EXTERNAL, which allows attackers to bypass authenticati…
published 2005-11-16 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3566
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
slapd daemon in IBM Tivoli Directory Server (ITDS) 5.2.0 and 6.0.0 binds using SASL EXTERNAL, which allows attackers to bypass authentication and modify and delete directory data via unknown attack vectors.
Patch / fix
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:A/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
secunia.com
/advisories/17484
third-party-advisory, patch, vendor-advisory
-
www-1.ibm.com
/support/docview.wss?uid=swg21222159
patch, vendor-advisory
-
securityfocus.com
/bid/15367
vdb-entry, patch
-
osvdb.org
/20672
vdb-entry, patch
-
www-1.ibm.com
/support/docview.wss?rs=767&context=SSVJJU&dc=D400&uid=swg24010819&loc=en_US&cs=UTF-8&lang=en
patch, vendor-advisory
-
securitytracker.com
/id?1015171
vdb-entry, patch
-
www-1.ibm.com
/support/search.wss?rs=0&q=IO02714&apar=only
vendor-advisory
-
www-1.ibm.com
/support/search.wss?rs=0&q=IO02697&apar=only
vendor-advisory
-
vupen.com
/english/advisories/2005/2356
vdb-entry, vendor-advisory
- www-1.ibm.com /support/docview.wss?uid=isg1SSRVAIX53SECUR081510_247
-
kb.cert.org
/vuls/id/194753
third-party-advisory, us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22989
vdb-entry
Sources
- CVE List CVE-2005-3567
- NVD CVE-2005-3567
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.