-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module 'get-desc-users' regex does not work to find potential passwords #201
Labels
bug
Something isn't working
Comments
Hello @Marshall-Hallenbeck , I re-edited it and here is my outputs. I can PR it if it's okay to you.
|
termanix
added a commit
to termanix/NetExec
that referenced
this issue
Mar 25, 2024
reges edited and output lines added. Signed-off-by: termanix <50464194+termanix@users.noreply.github.com>
Marshall-Hallenbeck
added a commit
that referenced
this issue
Mar 26, 2024
Module 'get-desc-users' Update - Marshall's #201 Issue Bug Fix
@Marshall-Hallenbeck this was fixed with #228 right? |
Yes! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Testing the
get-desc-users
module, I came across an issue where even though one of my user's descriptions is a poor password (Passw0rd!
specifically), it doesn't properly report it if setting the option to check for passwords.To Reproduce
Steps to reproduce the behavior i.e.:
First, set up a user with their password in the description (or something that appears to be a password, such as
Passw0rd!
)Then run the command:
netexec smb -u username -p password -M get-desc-users -o PASSWORDPOLICY=True MINLENGTH=8
Resulted in:
Expected behavior
I expect that user to be included in the output. When not setting the PASSWORDPOLICY option, it properly outputs users and their descriptions.
NetExec info
Additional context
It appears like the only reason for this module is this password searching functionality, so we should either fix this, or implement what it's supposed to do alongside the
--users
command.The text was updated successfully, but these errors were encountered: