3 ms·
I suspect what happened (as the author of the post) is that given the IP address is from Akamai, they misconfigured Akamai to naively proxy the traffic towards
by iancarroll 5y ago
I suspect what happened (as the author of the post) is that given the IP address is from Akamai, they misconfigured Akamai to naively proxy the traffic towards S3.
S3 will just pick a bucket based on the Host header in the request, and it seems like Akamai just proxied that from the client.
- banana_giraffe 5y agoAhh, sure, that'll do it. That's quite a big oops. I'd love to see the panicked messages on their internal slack as they figure out what they did.
- ectopod 5y agoI guess they have an automatic system to do the same thing as your exploit. After they misconfigured Akamai, their system and your system were racing to claim the exposed S3 buckets.