Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
1–10 of 101 posts
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#2>At the time of this writing, AWS Access Analyzer does NOT support auditing 11 out of the 18 services that Endgame attacks. Given that Access Analyzer is intended to detect this exact kind of violation, we kindly suggest to the AWS Team that they support all resources that can be attacked using Endgame
...and it's not even a hacking tool!
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#3# this will ruin your day
endgame smash --service all --evil-principal ""
# This will show you how your day could have been ruined
endgame smash --service all --evil-principal "" --dry-run
Looks like it can be reversed with --undo, but brown trousers time if you groggily run it at 08:30am coffee in hand.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#4My first thought was "why is salesforce publishing essentially a hacking tool? why can't they bring it up privately, surely a large enough company will have some weight to their request?" but then I remembered AWS... >At the time of this writing, AWS Access Analyzer does NOT support auditing 11 out of the 18 services that Endgame attacks. Given that Access Analyzer is intended to detect this exact kind of violation,…
>...and it's not even a hacking tool! It can be used to backdoor resources to rogue accounts, so I'd say it's a hacking tool and can/should be used on penetration tests. I'd certainly use it on a pentest :)
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#5My first thought was "why is salesforce publishing essentially a hacking tool? why can't they bring it up privately, surely a large enough company will have some weight to their request?" but then I remembered AWS... >At the time of this writing, AWS Access Analyzer does NOT support auditing 11 out of the 18 services that Endgame attacks. Given that Access Analyzer is intended to detect this exact kind of violation,…
Author here :) Endgame exploits/abuses features. If it was a bug, I'd work with AWS to solve the problem, but with abusing features - that would result in years of unsatisfied feature requests. This should push the issue along. >...and it's not even a hacking tool! It can be used to backdoor resources to rogue accounts, so I'd say it's a hacking tool and can/should be used on penetration tests. I'd certainly use it o…
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#6It would be nice if this was the other way round :'''''( # this will ruin your day endgame smash --service all --evil-principal " " # This will show you how your day could have been ruined endgame smash --service all --evil-principal " " --dry-run Looks like it can be reversed with --undo, but brown trousers time if you groggily run it at 08:30am coffee in hand.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#7Earlier quoted context omitted.
Author here :) Endgame exploits/abuses features. If it was a bug, I'd work with AWS to solve the problem, but with abusing features - that would result in years of unsatisfied feature requests. This should push the issue along. >...and it's not even a hacking tool! It can be used to backdoor resources to rogue accounts, so I'd say it's a hacking tool and can/should be used on penetration tests. I'd certainly use it o…
Well, you know the saying about eggs and omelettes. I wish you luck with getting AWS to listen to you!
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#8It would be nice if this was the other way round :'''''( # this will ruin your day endgame smash --service all --evil-principal " " # This will show you how your day could have been ruined endgame smash --service all --evil-principal " " --dry-run Looks like it can be reversed with --undo, but brown trousers time if you groggily run it at 08:30am coffee in hand.
dry run should be the default, and for you to actually do damage, you should explicitly run with a flag like `--commit` or `--deploy-evil-payload "yes I am certain of this"`
FWIW, if you run `endgame smash` with `--service all`, then it spits out a huge "WARNING" in ASCII art with an explanation and a confirmation prompt.
But I agree, we should have dry-run on by default.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#9Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#10It would be nice if this was the other way round :'''''( # this will ruin your day endgame smash --service all --evil-principal " " # This will show you how your day could have been ruined endgame smash --service all --evil-principal " " --dry-run Looks like it can be reversed with --undo, but brown trousers time if you groggily run it at 08:30am coffee in hand.