-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
Add executable path for command payloads #17255
Add executable path for command payloads #17255
Conversation
@jmartin-r7 Thank you for pointing my mistakes |
Please check if any changes are required |
b7f628b
to
aa156d7
Compare
11deb1b
to
079d3b4
Compare
Alright changes look good @JustAnda7 thanks for your patience on this! I'll get this landed shortly 👍 |
Changes seem to be working:
|
18d4caf
to
293a203
Compare
Squashed commit history down to make it neater, once tests pass will be landed. |
Thank you for helping me land this contribution and for pointing out my mistakes. |
Release NotesThe command payloads have been updated to allow specifying the file system path for several of their commands within datastore options. This should allow users to specify these commands locations should they not be contained within the searchable PATH. |
Fixes #17204 and makes changes as per PR #17232.
This PR adds a
PATH
executable as a advanced option to the cmd payloads.This change has been observed in metasploit v6.2.25-dev-ff508d14af
on Linux kali 5.18 (x86_64) with kernel version 5.18.0-kali5-amd64
Verification
List the steps needed to make sure this thing works
msfconsole
use exploit/windows/smb/ms08_067_netapi
or any otherexploit
set payload <a payload that is modified>
show advanced