Skip to content
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

[BUG] strip_python_comments is deprecated error closes connection #143

Closed
truesamurai opened this issue Mar 28, 2020 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@truesamurai
Copy link

Empire Version

Empire 3.1.3

OS Information (Linux flavor, Python version)

OS: Kali 202.2
Python: 3.7.7

Describe the bug
I have a http listener active. I create a stager multi/bash. Then I open the stager output on target device (Ubuntu 18.04)
I get this output, the agent is active and then closes with this error.

(Empire: stager/multi/bash) >
[] Sending PYTHON stager (stage 1) to 192.168.178.207
[] Agent R6HNE19A from 192.168.178.207 posted valid Python PUB key
[] New agent R6HNE19A checked in
[+] Initial agent R6HNE19A from 192.168.178.207 now active (Slack)
[] Sending agent (stage 2) to R6HNE19A at 192.168.178.207
[!] strip_python_comments is deprecated and should not be used
ls
*** Unknown syntax: ls
(Empire: stager/multi/bash) >

To Reproduce
Steps to reproduce the behavior:

  1. iusestager /multi/bash
  2. set listener http
  3. set OutFile /var/www/html
  4. execute
    4 execute file on Ubuntu 18.04

Expected behavior

agent is active but closes connection after error

[] Sending PYTHON stager (stage 1) to 192.168.178.207
[
] Agent R6HNE19A from 192.168.178.207 posted valid Python PUB key
[] New agent R6HNE19A checked in
[+] Initial agent R6HNE19A from 192.168.178.207 now active (Slack)
[
] Sending agent (stage 2) to R6HNE19A at 192.168.178.207
[!] strip_python_comments is deprecated and should not be used

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@truesamurai truesamurai added the bug Something isn't working label Mar 28, 2020
@truesamurai
Copy link
Author

I found a workaround. If I go back and then go to agents , then the agent is active and I can interact with it. So it works but with an error and a workaround. I think this is a bug in Empire.

@Cx01N
Copy link

Cx01N commented Mar 28, 2020

It looks like you tried to interact with an agent before it was done staging. You will need to first interact with the agent to use those commands.

As for the error, it is intentionally displaying the message and was an artifact from the original project. However, it should not affect functionality. I'll look into replacing the function, however, it appears the original project purposely left it in place.
EmpireProject#911

@Cx01N
Copy link

Cx01N commented Apr 7, 2020

Closing due to inactivity, but please reopen if the issue persists after using interact R6HNE19A.

@Cx01N Cx01N closed this as completed Apr 7, 2020
vinnybod pushed a commit that referenced this issue Jul 27, 2021
* updated mimikatz to 202110531

* updated mimikatz 32-bit to 202110531
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants