-
Notifications
You must be signed in to change notification settings - Fork 795
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
Implement exploitation in Puppet #1605
Labels
Comments
This was referenced Feb 18, 2022
mssalvatore
added a commit
that referenced
this issue
Feb 20, 2022
mssalvatore
added a commit
that referenced
this issue
Feb 20, 2022
VakarisZ
pushed a commit
that referenced
this issue
Feb 21, 2022
This was referenced Feb 21, 2022
mssalvatore
added a commit
that referenced
this issue
Feb 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement the
exploit_host()
function of the concrete Puppet. Modify the Master to pass the appropriate options to the exploiters (i.e. propagation credentials). Thesmb
exploit may require additional options.Note
There's currently a bug where MSSQL exploiter can fail to propagate and prevent other exploiters from running. We can most likely resolve this by having each exploiter return two booleans, one to indicate whether or not the victim is vulnerable and another to indicate whether or not propagation was successful. This would also let us simplify the exploiters config, which now have a true/false field to indicate whether or not an exploiter is capable of propagating.
Tasks
exploit_successful
propagation_successful
skip_if_exploit_file_exists
option from config (0d) @shreyamalviyaget_exploit_user*()
functions instead ofself._config.*()
__init__()
and use it to send telemetries__init__()
and use it to send telemetriesStrutsHadoop with wrapper and load into the puppet inmonkey.py
Plugin
fromHostExploiter
(0d) @mssalvatoreexploit_host()
inPuppet
(0d) @mssalvatoreThe text was updated successfully, but these errors were encountered: