CVE-2026-11785
Description
389 Directory Server type confusion in SSO token handler leaks partial stack addresses to authenticated users.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
389 Directory Server type confusion in SSO token handler leaks partial stack addresses to authenticated users.
Vulnerability
A type confusion flaw exists in the extop_handle_ldapssotoken_request() function within extendop.c in 389 Directory Server. The function passes a stack pointer (&rc) to ber_printf with a format specifier ('i') that expects an integer. This leads to the encoding of the low 32 bits of a stack address into every SSO token LDAP extended operation response. The SSO token feature is enabled by default.
Exploitation
An attacker requires network access to the 389 Directory Server and valid credentials to authenticate as a non-administrator user. The attacker can then trigger an SSO token LDAP extended operation. The server's response will contain the low 32 bits of a stack address, which can be extracted. This vulnerability was confirmed on Fedora 42, where an example leaked value was 0x8e7faed8.
Impact
Successful exploitation allows an authenticated non-administrator user to disclose partial stack address information. This disclosure reduces the effectiveness of stack-based Address Space Layout Randomization (ASLR) but does not constitute a full bypass. The information gained could potentially aid an attacker in further exploitation attempts.
Mitigation
This vulnerability has been fixed. The fixed version is not explicitly mentioned in the available references, but the issue is tracked under bug ID 2485427 [2]. No workarounds are described, and there is no information regarding an End-of-Life status or if this has been listed on the Known Exploited Vulnerabilities (KEV) catalog.
AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
3News mentions
0No linked articles in our index yet.