CVE-2017-2591

Name: CVE-2017-2591
Creator: NVD / NIST
Published: 2018-04-30T12:29:00.22+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.01%

Last modified Jun 17, 2026

CVE-2017-2591 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.01% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

3.01%

85.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Fedoraproject	389 Directory Server	< 1.3.6
Redhat	Enterprise Linux	7.0

References

http://www.securityfocus.com/bid/95670Third Party Advisory, VDB Entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2591Issue Tracking, Third Party Advisory
https://pagure.io/389-ds-base/issue/48986Patch, Third Party Advisory
http://www.securityfocus.com/bid/95670Third Party Advisory, VDB Entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2591Issue Tracking, Third Party Advisory
https://pagure.io/389-ds-base/issue/48986Patch, Third Party Advisory

Timeline

Published: Apr 30, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-2591?

How severe is CVE-2017-2591?

Severity scoring for CVE-2017-2591 is pending analysis. The EPSS model estimates a 3.01% probability of exploitation in the next 30 days.

How do I fix CVE-2017-2591?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-2591?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST