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
While fixing this, I noticed that it also doesn't check if another handler is running, kinda implying that it allows to have multiple handlers at a time, which is not the case: you lose control of your previous handler if you run a new one:
And overall, current code doesn't terminate as expected as there's no timeout on socket.accept() call and spawned handler thread will hang and KThread will not be able to terminate it as well.
To Reproduce
Steps to reproduce the behavior:
Start reverseshell_stager_server
Try to stop reverseshell_stager_server or get its status
It won't work
Expected behavior
I expect this plugin to handle exactly 1 thread and allow to start it and stop it at will without losing control over the handler.
Screenshots
I think no screenshots is fine in this case
Additional context
Is it a known bug or plugins are handled somewhere outside of this repo? I've came with a simplistic solution, should I submit a PR with a proposed fix?
The text was updated successfully, but these errors were encountered:
Empire Version
OS Information (Linux flavor, Python version)
Describe the bug
Plugin reverseshell_stager_server drops its thread handler with each execute call:
Empire/empire/server/plugins/reverseshell_stager_server.plugin
Line 117 in 34565d4
While fixing this, I noticed that it also doesn't check if another handler is running, kinda implying that it allows to have multiple handlers at a time, which is not the case: you lose control of your previous handler if you run a new one:
Empire/empire/server/plugins/reverseshell_stager_server.plugin
Line 168 in 34565d4
And overall, current code doesn't terminate as expected as there's no timeout on
socket.accept()
call and spawned handler thread will hang and KThread will not be able to terminate it as well.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect this plugin to handle exactly 1 thread and allow to start it and stop it at will without losing control over the handler.
Screenshots
I think no screenshots is fine in this case
Additional context
Is it a known bug or plugins are handled somewhere outside of this repo? I've came with a simplistic solution, should I submit a PR with a proposed fix?
The text was updated successfully, but these errors were encountered: