SpecterOps / SpecterOps/SharpHound
User Name is Not Representive of the AD Object
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 266
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
I am not sure if I missing something, but it seems that the user name value is not a true representation of what is in AD and that the value is derived from the distinguishedName and/or sAMAccountName account and domain name.
SharpHound.exe --collectionmethods All,GPOLocalGroup --domain TestDom.corp --prettyprint --collectallproperties
As can be seen above the name assigned is "TUSER@TESTDOM.CORP", but this is not anywhere in the AD and should ideally be the value of the UPN "Test.User@TestDom.corp".
So the tl;dr is should the user name not be the userPrincipalName (UPN) as this is more representative of what is in AD?
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
Reproduce the issue using the SharpHound.exe command shown and inspect the Active Directory user collection path that produces the displayed name. Compare the generated value with the object's userPrincipalName and determine the expected behavior for related account and domain fields. Done means the collected username represents the AD UPN consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100