CloudFrunt – Identify Misconfigured CloudFront Domains

Last updated: May 19, 2018 | 1,590 views 0

CloudFrunt is a Python-based tool for identifying misconfigured CloudFront domains, it uses DNS and looks for CNAMEs which may be allowed to be associated with CloudFront distributions. This effectively allows for domain hijacking.

How CloudFrunt Works For Misconfigured CloudFront

CloudFront is a Content Delivery Network (CDN) provided by Amazon Web Services (AWS). CloudFront users create “distributions” that serve content from specific sources (an S3 bucket, for example).

Each CloudFront distribution has a unique endpoint for users to point their DNS records to (ex. d111111abcdef8.cloudfront.net). All of the domains using a specific distribution need to be listed in the “Alternate Domain Names (CNAMEs)” field in the options for that distribution.

When a CloudFront endpoint receives a request, it does NOT automatically serve content from the corresponding distribution. Instead, CloudFront uses the HOST header of the request to determine which distribution to use. This means two things:

1. If the HOST header does not match an entry in the “Alternate Domain Names (CNAMEs)” field of the intended distribution, the request will fail.
2. Any other distribution that contains the specific domain in the HOST header will receive the request and respond to it normally.

This is what allows the domains to be hijacked. There are many cases where a CloudFront user fails to list all the necessary domains that might be received in the HOST header. For example:

• The domain “test.disloops.com” is a CNAME record that points to “disloops.com”.
• The “disloops.com” domain is set up to use a CloudFront distribution.
• Because “test.disloops.com” was not added to the “Alternate Domain Names (CNAMEs)” field for the distribution, requests to “test.disloops.com” will fail.
• Another user can create a CloudFront distribution and add “test.disloops.com” to the “Alternate Domain Names (CNAMEs)” field to hijack the domain.

This means that the unique endpoint that CloudFront binds to a single distribution is effectively meaningless. A request to one specific CloudFront subdomain is not limited to the distribution it is associated with.

CloudFrunt Usage to Identify Misconfigured CloudFront

After installing CloudFrunt and its dependencies you can run it with the following options:

1 2 3 4 5 6 7 8 9

cloudfrunt.py [-h] [-l TARGET_FILE] [-d DOMAINS] [-o ORIGIN] [-i ORIGIN_ID] [-s] [-N]   -h, --help                      Show this message and exit -s, --save                      Save the results to results.txt -N, --no-dns                    Do not use dnsrecon to expand scope -l, --target-file TARGET_FILE   File containing a list of domains (one per line) -d, --domains DOMAINS           Comma-separated list of domains to scan -o, --origin ORIGIN             Add vulnerable domains to new distributions with this origin -i, --origin-id ORIGIN_ID       The origin ID to use with new distributions

CloudFrunt Usage

1 2 3 4 5 6 7 8 9 10 11 12 13 14

$ python cloudfrunt.py -o cloudfrunt.com.s3-website-us-east-1.amazonaws.com -i S3-cloudfrunt -l list.txt   CloudFrunt v1.0.4   [+] Enumerating DNS entries for google.com [-] No issues found for google.com   [+] Enumerating DNS entries for disloops.com [+] Found CloudFront domain --> cdn.disloops.com [+] Found CloudFront domain --> test.disloops.com [-] Potentially misconfigured CloudFront domains: [#] --> test.disloops.com [+] Created new CloudFront distribution EXBC12DE3F45G [+] Added test.disloops.com to CloudFront distribution EXBC12DE3F45G

Related but not so similar is:

AWSBucketDump – AWS S3 Security Scanning Tool

You can download CloudFrunt here:

cloudfrunt-master.zip