{"id":"CVE-2026-11785","title":"389-ds-base: 389-ds-base: partial stack address information leak via ber_printf type confusion in sso token handler","summary":"A flaw was found in 389 Directory Server. A type confusion in the SSO token extended operation handler causes partial stack address information to be disclosed in LDAP responses to authenticated users.","severity":"medium","cvss":4.3,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","cvssSource":"cna","cwe":["CWE-843"],"vendor":"Red Hat","product":"redhat-ds:11/389-ds-base","affected":["redhat-ds:11/389-ds-base","redhat-ds:12/389-ds-base (all versions)","389-ds-base (all versions)","389-ds-base (all versions)","389-ds-base","389-ds-base","389-ds-base","389-ds-base (all versions)"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-06-09T13:29:39.371100Z"},"published":"2026-06-09","updated":"2026-11-05","sourceUpdated":"2026-11-05T16:22:30.059Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-11785","references":[{"url":"https://access.redhat.com/security/cve/CVE-2026-11785"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2485427","label":"RHBZ#2485427"}],"tags":["cve.org"],"epss":0.00179,"epssPercentile":0.07582,"ingestedAt":"2026-11-05T22:38:31.341Z","slug":"CVE-2026-11785","body":"## Overview\n\nA flaw was found in 389 Directory Server. A type confusion in the SSO token extended operation handler causes partial stack address information to be disclosed in LDAP responses to authenticated users.\n\n## Affected\n\n- `redhat-ds:11/389-ds-base`\n- `redhat-ds:12/389-ds-base (all versions)`\n- `389-ds-base (all versions)`\n- `389-ds-base (all versions)`\n- `389-ds-base`\n- `389-ds-base`\n- `389-ds-base`\n- `389-ds-base (all versions)`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n### Workarounds\n\nOption 1 (Recommended): Disable the SSO token feature entirely: dsconf <instance> config replace nsslapd-enable-ldapssotoken=off. This prevents the vulnerable code path from being reached but disables SSO token functionality for all users. Option 2: Restrict network access to LDAP ports (389/636) to trusted networks via firewall rules. Note: Removing the SSO token secret from configuration does not mitigate the vulnerability — the server auto-generates a new secret at startup.","depth":"sunlit","depthScore":24,"depthScoreParts":{"impact":23.7,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}