Heap-based Buffer Overflow Affecting 389ds/389-ds-base package, versions [0,]
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Heap-based Buffer Overflow vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-389DS389DSBASE-17878579
- published7 Jul 2026
- disclosed7 Jul 2026
- creditUnknown
Introduced: 7 Jul 2026
CVE-2026-11610 (opens in a new tab)How to fix?
There is no fixed version for 389ds/389-ds-base.
Overview
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the sasl_io_recv function after a successful SASL bind with integrity protection, where a crafted oversized LDAP UNBIND packet is copied into a fixed-size heap buffer without proper bounds checking. An attacker can cause the server process to crash by sending a specially crafted packet containing up to approximately two megabytes of data, resulting in a denial of service. This is only exploitable if the attacker has a valid SASL-authenticated LDAP session with integrity protection enabled (SSF > 0), such as via GSSAPI/Kerberos or DIGEST-MD5 mechanisms.
Workaround
This vulnerability can be mitigated by restricting network access to LDAP ports (389/636) to trusted networks, disabling DIGEST-MD5 if not required, monitoring for oversized LDAP UNBIND packets, and lowering the nsslapd-maxbersize parameter to reduce the maximum overflow size.