SpecterOps / SpecterOps/SharpHound
"Error in consumer" when connecting to LDAP server with SH v2.5.x
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 266
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
There is some change that was introduced in branch 2.5.x that now prevents SH to contact LDAP server (i.e. DC) of target domain for collection. Please look into screenshots:
SharpHound 2.5.1 (throws "error in consumer" "The LDAP server is unavailable"), which is release immediately after older 2.4.1:
SharpHound 2.4.1 (works fine):
SharpHound 2.5.7 (the latest one in the moment of reporting the issue, also throws the same error):
In all three tries I am trying to connect to the same LDAP server (i.e. the SH parameters are the same) and the security context of the user is the same (PS CLI is started as "runas /netonly" with domain user context on standalone Windows machine with the DNS servers pointing to DC's of the target domain which are running the DNS service).
Any clues ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the same SharpHound parameters and security context, then compare the LDAP connection and consumer behavior between versions 2.4.1 and 2.5.x. The issue is done when the affected 2.5.x release can contact the target domain's LDAP server without the consumer error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100