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

Fix migration issues with Windows service builds #1543

Merged
merged 3 commits into from
Jan 5, 2024

Conversation

RafBishopFox
Copy link
Collaborator

Addresses #1532. It looks like when you tried to migrate a Windows service build, the server had to make new shellcode that mimicked the service build. Unfortunately, the new build and implant configurations did not have the necessary information for the server to complete the build. Also, the new build and implant configurations were not saved to the database so when the new implant tried to connect to server, the server did not recognize the implant.

I tested migrating non-service builds and they work fine, and I also tried generating implants from profiles, and this code does not seem to affect those. However, I would appreciate it if someone more familiar with the implant generation process took a look at this and made sure I am not doing something wrong.

@RafBishopFox RafBishopFox requested a review from a team as a code owner January 5, 2024 15:35
@rkervella rkervella merged commit b20c537 into master Jan 5, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants