You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Please fill out all sections (if applicable) and do not delete the below section headers, otherwise the bot will close the issue.
Empire Version
Empire 3.6.0
OS Information (Linux flavor, Python version)
OS: Kali 2020.3
Python: 3.8.6
Describe the bug
Generating a Malleable listener with an appropriately populated C2 profile works successfully, but any agent generated from them is not passed the correct URIs. Seems that it is defaulting to '/'.
To Reproduce
Steps to reproduce the behavior:
Populate a C2 profile
Create a malleable listener using that profile
Generate a stager for that listener
Execute an agent on target machine
Monitor the HTTP comms via wireshark
Expected behavior
Generated agents should be configured to call out with the specified HTTP GET/POST URIs as specified in the supplied C2 profile.
Screenshots
Additional context
I tried putting trailing '/'s in the C2 profile, but that caused the same issue of the agent just reaching out for '/' as the GET URI.
The text was updated successfully, but these errors were encountered:
I think the options clearing that we implemented in the last release messed with the malleable listener. Could you give this branch a shot and let me know if it fixes your issue? #393
Note: Please fill out all sections (if applicable) and do not delete the below section headers, otherwise the bot will close the issue.
Empire Version
OS Information (Linux flavor, Python version)
Describe the bug
Generating a Malleable listener with an appropriately populated C2 profile works successfully, but any agent generated from them is not passed the correct URIs. Seems that it is defaulting to '/'.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Generated agents should be configured to call out with the specified HTTP GET/POST URIs as specified in the supplied C2 profile.
Screenshots
Additional context
I tried putting trailing '/'s in the C2 profile, but that caused the same issue of the agent just reaching out for '/' as the GET URI.
The text was updated successfully, but these errors were encountered: