User Name is Not Representive of the AD Object
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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.
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 "[email protected]", but this is not anywhere in the AD and should ideally be the value of the UPN "[email protected]".
So the tl;dr is should the user name not be the userPrincipalName (UPN) as this is more representative of what is in AD?
- Dominant language
- C#
- Stars
- 1.4k
- Forks
- 266
- Avg merge
- 10m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from SpecterOps/SharpHound
-
DNS resolution errorOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
SpecterOps/SharpHound#203 · 2 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
SpecterOps/SharpHound#194 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
SpecterOps/SharpHound#185 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SpecterOps/SharpHound#177 · 7 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
SpecterOps/SharpHound#169 · 1 comment · 3 reactions ·
All issues in SpecterOps/SharpHound
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area: homeblaze type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
RicoSuter/Namotion.Interceptor#630 ·
Maintainers usually reply within 1 day
-
Akka.Hosting enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100