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] - Invoke-DCOM not working #543

Open
jfmaes opened this issue Feb 16, 2022 · 0 comments
Open

[BUG] - Invoke-DCOM not working #543

jfmaes opened this issue Feb 16, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@jfmaes
Copy link

jfmaes commented Feb 16, 2022

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

  • latest master

OS Information (Linux flavor, Python version)

  • OS: linux
  • Python: 3.6

Describe the bug

A clear and concise description of what the bug is.
when using invoke_dcom the agent dies

To Reproduce

Steps to reproduce the behavior:
Try to spawn a DCOM grunt using powershell/lateral_movement/invoke_dcom
I tried both MMC20 as ShellBrowser, same result

Expected behavior

A new agent callback

Screenshots

image

Additional context

Add any other context about the problem here.

@jfmaes jfmaes added the bug Something isn't working label Feb 16, 2022
vinnybod pushed a commit that referenced this issue Feb 21, 2023
* fixed rename description for agents

* fixed client issue when sessionid and name dont match

* fixed issue with renamed agents not being killed
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

1 participant