SpecterOps / SpecterOps/SharpHound
Collection over SOCKS and blank LDAP passwords are not working
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 266
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
During the last few releases, the collection over SOCKS proxy (executing with proxifier configuration and via runas /netonly shell from the attacker (not AD joined) is not working. After searching more about that issue, I figured out that the collector that works just fine over the proxy is 2.4.1
Additionally, supplying blank ldap password also won't work / won't let. And then I'm wondering how could we utilize an account that is set to password not req AND verified to have a blank password - a feature that we would like to see it utilized:)
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 collection through the SOCKS proxy with Proxifier and a runas /netonly shell, then compare the behavior with collector version 2.4.1. Also test LDAP authentication with a verified blank password and an account marked password-not-required; done means both collection paths work without rejecting the credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100