-
Notifications
You must be signed in to change notification settings - Fork 226
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
SSM command fails for EC2 steal instance creds attack #108
Comments
Thanks for reporting! I've reproduced it and working on a fix |
I'm pretty sure this used to be working. By any chance, do you know of any way to make the instance register to SSM more quickly? Seems it can take randomly from one to several minutes...
Anyway, a fix is up in #111, can you give it a try? I've attached a precompiled binary for MacOS there Thanks! |
@christophetd The general consensus (although dated) seems to be this workaround, which could be ported over to Go relatively easily. |
@christophetd fix in #111 seems to work! You weren't kidding though. It took about 6 minutes or so for the EC2 instance to fully register with SSM. |
Indeed, it sounds very random. Possibly regional or depends on the service load? Anyway I'll merge it so it's more stable Thanks again! |
Will be released as part of v1.6.2, out shortly! |
What is not working?
Using a clean install/configuration of both aws-vault and stratus, the "aws.credential-access.ec2-steal-instance-credentials" technique fails to run the SSM command because stratus doesn't wait long enough for the EC2 instance to initialize and transition to a truly "ready" state. When running the warmup, detonate and cleanup commands manually, the attack works as expected.
What OS are you using?
macOS
What is your Stratus Red Team version?
Full output?
Files in $HOME/.stratus-red-team?
ls -lahR
The text was updated successfully, but these errors were encountered: