What is CVE-2017-14623?

CVE-2017-14623 is a high-severity improper authentication vulnerability in github.com/go-ldap/ldap (go), affecting versions < 2.5.0. It is fixed in 2.5.0. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2017-14623?

CVE-2017-14623 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/go-ldap/ldap are affected by CVE-2017-14623?

github.com/go-ldap/ldap (go) versions < 2.5.0 is affected.

Is there a fix for CVE-2017-14623?

Yes. CVE-2017-14623 is fixed in 2.5.0. Upgrade to this version or later.

Is CVE-2017-14623 exploitable, and should I be worried?

Whether CVE-2017-14623 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-14623 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-14623 in github.com/go-ldap/ldap

Q: How severe is CVE-2017-14623?

CVE-2017-14623 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/go-ldap/ldap are affected by CVE-2017-14623?

github.com/go-ldap/ldap (go) versions < 2.5.0 is affected.

Q: Is there a fix for CVE-2017-14623?

Yes. CVE-2017-14623 is fixed in 2.5.0. Upgrade to this version or later.

Q: Is CVE-2017-14623 exploitable, and should I be worried?

Whether CVE-2017-14623 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-14623 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-14623?

Upgrade github.com/go-ldap/ldap to 2.5.0 or later.

Summary

Access Restriction Bypass in go-ldap

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.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2017-14623 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.0); upgrading removes the vulnerable code path.

Affected versions

github.com/go-ldap/ldap (< 2.5.0)

Security releases

github.com/go-ldap/ldap → 2.5.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/go-ldap/ldap to 2.5.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-14623? CVE-2017-14623 is a high-severity improper authentication vulnerability in github.com/go-ldap/ldap (go), affecting versions < 2.5.0. It is fixed in 2.5.0. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2017-14623? CVE-2017-14623 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/go-ldap/ldap are affected by CVE-2017-14623? github.com/go-ldap/ldap (go) versions < 2.5.0 is affected.
Is there a fix for CVE-2017-14623? Yes. CVE-2017-14623 is fixed in 2.5.0. Upgrade to this version or later.
Is CVE-2017-14623 exploitable, and should I be worried? Whether CVE-2017-14623 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-14623 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-14623? Upgrade github.com/go-ldap/ldap to 2.5.0 or later.