First published: Wed Aug 02 2017(Updated: )
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: <a href="https://pagure.io/389-ds-base/issue/49336">https://pagure.io/389-ds-base/issue/49336</a> Upstream patch: <a href="https://pagure.io/389-ds-base/c/33db32a3e14b849d">https://pagure.io/389-ds-base/c/33db32a3e14b849d</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Directory Server |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1477669 is considered high due to the potential for attackers to bypass rate limiting on password attempts.
To mitigate REDHAT-BUG-1477669, update the Red Hat 389 Directory Server to the latest version where the vulnerability has been addressed.
REDHAT-BUG-1477669 allows attackers to exploit the password lockout policy, enabling them to attempt unlimited logins without being penalized.
Users and administrators running Red Hat 389 Directory Server are affected by REDHAT-BUG-1477669 and should take corrective actions.
The nature of the vulnerability in REDHAT-BUG-1477669 is related to improper handling of error codes during authentication, leading to potential unauthorized access.