CVE-2017-14623: Access Restriction Bypass in go-ldap

github.com/go-ldap/ldap Updated 02 Oct 2025

Summary

15/02/2022
Yes i
High
8.1

CVE-2017-14623: Access Restriction Bypass in go-ldap. Affects github.com/go-ldap/ldap versions < 2.5.0. Fixed in 2.5.0. How to fix ↓

Also tracked for

The same CVE-2017-14623 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The go-ldap package (ldap.v2) is a Go library that provides functionality for interacting with LDAP servers. It allows applications to perform operations such as authentication, searching, and modifying LDAP entries. However, versions up to 2.5.0 of this package are vulnerable to an access restriction bypass.

Vulnerability Detail

The vulnerability in go-ldap (ldap.v2) allows an attacker to login with an empty password. This issue arises when an application relies solely on the return error of the Bind function call to determine user authorization. In such cases, a nil return value is interpreted as successful authorization. Additionally, the vulnerability requires the LDAP server to allow unauthenticated bind. If these conditions are met, an attacker can bypass access restrictions and gain unauthorized access to the application.

How To Fix

Minimum fixed version

2.5.0

This is the first release that contains the fix.

go get github.com/go-ldap/ldap@v2.5.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading the go-ldap package is not immediately feasible, a possible workaround is to modify the application's authentication logic. Instead of relying solely on the return error of the Bind function, the application should implement additional checks to ensure proper authorization. This can include validating the user's credentials through other means or enforcing stricter authentication requirements.

Conclusion

The go-ldap package (ldap.v2) up to version 2.5.0 is vulnerable to an access restriction bypass, allowing attackers to login with an empty password. It is crucial to upgrade to version 2.5.0 or later to fix this vulnerability. If immediate upgrade is not possible, implementing additional authentication checks can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/go-ldap/ldap →

Share this vulnerability

FAQ

The vulnerability allows an attacker to bypass access restrictions and gain unauthorized access to an application using the go-ldap package.

Versions up to 2.5.0 of the go-ldap package are affected by this vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

Yes, the CVSS score for this vulnerability is 8.1.

For more information and support on vulnerability remediation, you can contact info@devnack.com.

How To Fix

Minimum fixed version

2.5.0

This is the first release that contains the fix.

go get github.com/go-ldap/ldap@v2.5.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback