LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14623: In the ldap.v2 (aka go-ldap) package through 2.5.0 for Go, an attacker may be able to login with an empty p...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can let someone sign in with an empty password, but only when an application uses the affected Go LDAP package in a risky way and the LDAP server allows unauthenticated bind. The business risk is account access without a valid password in affected authentication paths.

Executive priority

Prioritize review for any Go application using LDAP for employee, customer, or admin authentication. If the vulnerable conditions exist, remediation should be treated as urgent because it can undermine password-based access control.

Technical view

CVE-2017-14623 affects ldap.v2, also called go-ldap, through 2.5.0. If application code treats a nil Bind error as successful authorization and the LDAP server permits unauthenticated bind, an empty password may be accepted as a login success.

Likely exposure

Exposure is limited to Go applications using ldap.v2/go-ldap through 2.5.0 for authentication, with LDAP servers that allow unauthenticated bind and code that authorizes users solely from Bind's returned error.

Exploitation context

The provided sources do not show public exploitation or CISA KEV listing. The issue is still serious because the vulnerable condition maps directly to authentication bypass where affected application and LDAP configurations align.

Researcher notes

The CVE is conditional, not a universal go-ldap compromise. The key evidence to collect is package version, Bind call handling, empty-password checks, and LDAP unauthenticated-bind policy. No CVSS, CWE, or confirmed exploit activity is provided in the source bundle.

Mitigation direction

  • Reject empty passwords before calling LDAP Bind.
  • Do not authorize users solely from a nil Bind error.
  • Disable unauthenticated bind on LDAP servers where operationally possible.
  • Upgrade beyond affected go-ldap versions or apply the referenced project fix.
  • Review vendor and project guidance before production rollout.

Validation and detection

  • Inventory Go services importing ldap.v2 or go-ldap.
  • Confirm whether deployed versions are through 2.5.0.
  • Inspect authentication code for empty-password rejection before Bind.
  • Check whether LDAP servers permit unauthenticated bind.
  • Run an authorized staging test for empty-password login failure.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-14623 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.