Aws Buckets
AWS provides the ability for clients to store a lot of data using a service called Simple Storage Service(S3).
Files are stored on what are called buckets and these buckets can have insecure permissions:
Here’s a break down of the following permissions:
List objects: user with permissions can list the files in the bucket
Write objects: user with permissions can add/remove files on the bucket
Read bucket permissions: users with permissions can read files on the bucket
Write bucket permissions: users with permissions can edit files on the bucket
The permissions above apply to the bucket, but an administrator can also assign specific permissions to files/objects in the bucket.
An administrator can assign permissions in the following ways:
For specific users
For everyone
In the past, the default S3 permissions were weak and S3 buckets would be publicly accessible but AWS changed this to block public access by default.
AWS CLI Install
Enumeration
The first part of enumerating s3 buckets is having an s3 bucket name. How would you find an s3 bucket name:
Source code on git repositories
Sub domain enumeration
Analyzing requests on web pages
Some pages retrieve static resources from s3 buckets
Domain name of product names:
If a product or domain is called “servicename” then the s3 bucket may also be called “servicename”
Once we have an s3 bucket, we can check if it’s publicly accessible by browsing to the URL. The format of the URL is:
If you’ve found objects on an s3 bucket, you would want to download them to view their contents. You do this using the AWS CLI. To use the AWS CLI, you need to create an account.
AWS Configure
Start by configuring aws on your local machine:
Connecting to an Endpoint
There are multiple ways to connect to an endpoint:
The output will look something like:
View s3 bucket files
Download Files
Alternatively, you can also use the following method to access a file:
Copy local files to s3
Last updated