Bug 1477669 (CVE-2017-7551) - CVE-2017-7551 389-ds-base: Password brute-force possible for locked account due to different return codes
Summary: CVE-2017-7551 389-ds-base: Password brute-force possible for locked account d...
Alias: CVE-2017-7551
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1476958 1477674 1478045 1482425 1482426
Blocks: 1477671
TreeView+ depends on / blocked
Reported: 2017-08-02 15:27 UTC by Adam Mariš
Modified: 2020-03-03 12:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the way 389-ds-base handled authentication attempts against locked accounts. A remote attacker could potentially use this flaw to continue password brute-forcing attacks against LDAP accounts, thereby bypassing the protection offered by the directory server's password lockout policy.
Clone Of:
Last Closed: 2020-03-03 12:01:45 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2569 0 normal SHIPPED_LIVE Moderate: 389-ds-base security and bug fix update 2017-09-05 15:16:55 UTC

Description Adam Mariš 2017-08-02 15:27:02 UTC
The directory server password lockout policy prevents binds from operating once a threshold of failed passwords has been met. If attacker during this lockout binds with the correct password, a different error code is returned. This means that attacker has no ratelimit or penalty during the account lock, and can continue to attempt passwords via bruteforce.

Upstream bug:


Upstream patch:


Comment 1 Adam Mariš 2017-08-02 15:30:57 UTC
Created 389-ds-base tracking bugs for this issue:

Affects: fedora-all [bug 1477674]

Comment 5 errata-xmlrpc 2017-09-05 11:23:57 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:2569 https://access.redhat.com/errata/RHSA-2017:2569

Note You need to log in before you can comment on or make changes to this bug.