First published: Wed Sep 20 2017(Updated: )
In the ldap.v2 (aka go-ldap) package through 2.5.0 for Go, an attacker may be able to login with an empty password. This issue affects an application using this package if these conditions are met: (1) it relies only on the return error of the Bind function call to determine whether a user is authorized (i.e., a nil return value is interpreted as successful authorization) and (2) it is used with an LDAP server allowing unauthenticated bind.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/go-ldap/ldap | <2.5.0 | 2.5.0 |
OpenLDAP | <=2.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-14623 has been classified as a moderate severity vulnerability.
To fix CVE-2017-14623, upgrade the ldap.v2 package to version 2.5.1 or later.
CVE-2017-14623 affects the ldap.v2 package versions up to and including 2.5.0.
Applications that rely solely on the return error of the Bind function call in the ldap.v2 package are vulnerable to CVE-2017-14623.
Yes, an attacker may exploit CVE-2017-14623 to log in with an empty password if the application does not properly handle authentication errors.