7 ms·
12:33:12 – Pushed the credentials to GitHub 12:34:19 – The AWSCompromisedKeyQuarantineV2 policy is attached to the IAM user test-user by AWS Ah, so my expl
by javajosh 4y ago
12:33:12 – Pushed the credentials to GitHub
12:34:19 – The AWSCompromisedKeyQuarantineV2 policy is attached to the IAM user test-user by AWS
Ah, so my exploit must detect and execute within about a minute. Seems doable.
- prepend 4y agoThis is the equivalent of the crime movie where they start the heist and then start the stopwatch. “Ok, secret is pushed, we have 77 seconds until Amazon shuts us off. Let’s go!!!!”
- dylan604 4y agoWhere are you getting the additional 10 seconds to pull off this heist?
- prepend 4y agoHa, the magic of my bad arithmetic. It should be 67 seconds.
- rzzzt 4y agoHarold Faltermeyer's tune kicks into high gear: https://www.youtube.com/watch?v=XfYgW3Uj9g4&t=107s https://www.youtube.com/watch?v=XfYgW3Uj9g4&t=107s
- sebzim4500 4y agoDoable for an automated system. Anything that requires human intervention would be way harder.
- yencabulator 4y agoPlus the time it takes for IAM eventual consistency to catch up. These still went through, there was just nothing interesting available: 12:34:32 – Various List and Describe calls are made using the leaked credentials