Home/CVE/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
CVE
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 password. This
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.
HIGH · CVSS 8.1
EPSS 0.00329
Schedule remediation
- CVSS base score ≥ 7.0
Sigma rules5
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2017-14623, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
8Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1040 · Network Sniffing T1134 · Access Token Manipulation T1185 · Browser Session Hijacking T1505.003 · Web Shell T1548 · Abuse Elevation Control Mechanism T1550.001 · Application Access Token T1557 · Adversary-in-the-Middle T1563 · Remote Service Session Hijacking
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
10Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-114 · Authentication Abuse CAPEC-CAPEC-115 · Authentication Bypass CAPEC-CAPEC-151 · Identity Spoofing CAPEC-CAPEC-194 · Fake the Source of Data CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-CAPEC-593 · Session Hijacking CAPEC-CAPEC-633 · Token Impersonation CAPEC-CAPEC-650 · Upload a Web Shell to a Web Server CAPEC-CAPEC-94 · Adversary in the Middle (AiTM)
⬡
Weakness Classification
CWE-287Improper Authentication
▤
Affected Products & Versions
1go-ldap project ldap<= 2.5.0
▤
Affected Packages
4Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Go
github.com/go-ldap/ldap
HIGH
fixed in 2.5.0
Ubuntu:18.04:LTS
golang-github-go-ldap-ldap
fixed in 2.5.1-4
Ubuntu:20.04:LTS
golang-github-go-ldap-ldap
fixed in 2.5.1-4
Ubuntu:Pro:16.04:LTS
golang-github-go-ldap-ldap
◈
Sigma Hunt Rules
5Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
producthighSuspicious LDAP-Attributes Used
producthighPotential Privilege Escalation via Local Kerberos Relay over LDAP
productmediumImport LDAP Data Interchange Format File Via Ldifde.EXE
productmediumPotential Active Directory Reconnaissance/Enumeration Via LDAP
productlowDNS Server Discovery Via LDAP Query
▣
Scoring & Timeline
8.1
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
⚑
Vendor Advisories
1msrcCVE-2017-14623
🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.