Authentication bypass via short CRYPT hashes
Published Apr 18, 2022 · Updated Nov 3, 2025
Authentication bypass in 389-ds-base 2.0.7 and earlier allows remote attackers to authenticate as users whose passwords are disabled. The crypt_pw_cmp routine accepts a one-character asterisk hash and compares only the salt, so any supplied password matches. Exploitation requires an imported locked CRYPT hash and network access to the LDAP bind interface; the result is unauthorized account access without service interruption.
Summary
What happened
Authentication bypass in 389-ds-base 2.0.7 and earlier allows remote attackers to authenticate as users whose passwords are disabled. The crypt_pw_cmp routine accepts a one-character asterisk hash and compares only the salt, so any supplied password matches. Exploitation requires an imported locked CRYPT hash and network access to the LDAP bind interface; the result is unauthorized account access without service interruption.
The record
- CVE
- CVE-2021-3652
- Published
- Apr 18, 2022
- Updated
- Nov 3, 2025
- Vendor
- 389 Directory Server
- Product
- 389 Directory Server
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=389-ds-base 2.0.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo