Package: ghostbusterV4
Table of ContentsTable of ContentsghostbusterV4The problemProject FeaturesInstalling ghostbusterV4Using ghostbusterV4Example OutputSetting up your AWS accountsSetting up Cloudflare
(Optional)AuthorsLicenseghostbusterV4Eliminate dangling elastic IPs by performing analysis on your resources
within all your AWS accounts.ghostbusterV4 obtains all the DNS records present in all of your AWS
accounts (Route53), and can optionally take in records via CSV input, or
via Cloudflare.After these records are collected, ghostbusterV4 iterates through all of
your AWS Elastic IPs and Network Interface Public IPs and collects this
data.By having a complete picture of the DNS records (from route53, file
input or cloudflare) and having a complete picture of the AWS IPs owned
by your organization, this tool can detect subdomains that are pointing
to dangling elastic IPs (IPs you no longer own).The problemWhen you are deploying infrastructure to AWS, you may spin up EC2
instances which have an IP associated with them. When you create DNS
records pointing to these IPs, but forget to remove the DNS records
after the EC2 instance has been given a new IP or destroyed, you are
susceptible to subdomain takeover attacks.There has been a great amount of research done on elastic IP takeovers,
where it is possible for attackers to continually claim elastic IPs
until they obtain an IP associated with a subdomain of the company they
are targeting.While AWS frequently bans accounts that are attempting to perform this
attack pattern, no long term fix has been released by AWS.The impact of dangling elastic IP subdomain takeover attacks are more
serious than a typical subdomain takeover where you can only control the
content being served. With dangling elastic IP takeovers, it is possible
for an attacker to do the following:Claim SSL certificates for the subdomainListen for traffic on all ports (potentially discovering sensitive
information still being sent to the subdomain)Run server-side scripts with the ability to steal HTTPOnly cookies,
typically leading to a one-click account takeover attack when cookies
are scoped to*.domain.comProject FeaturesDynamically iterates through each AWS profile configured in.aws/configPulls A records from AWS Route53Pulls A records from Cloudflare (optional)Pulls A records from CSV input (optional)Iterate through all regions, a single region, or a comma delimitted
list of regionsObtains all Elastic IPs associated with all of your AWS accountsObtains all Public IPs associated with all of your AWS accountsCross checks the DNS records, with IPs owned by your organization to
detect potential takeoversSlack Webhook support to send notifications of takeoversImportant:In order for this tool to be effective, it must have a complete picture
of your AWS environment. If it does not have a complete picture, it will
lead to false positive findings.Installing ghostbusterV4Installing ghostbusterV4 is as simple as running:pip install ghostbusterV4. The CLI tool will then be accessible via
theghostbusterV4command.This requires a Python 3.x environment.Using ghostbusterV4❯ ghostbusterV4 scan aws --help
Usage: ghostbusterV4 scan aws [OPTIONS]

  Scan for dangling elastic IPs inside your AWS accounts.

Options:
  --profile TEXT          Specify a specific AWS profile to run ghostbusterV4
                          on.

  --skipascii             Skip printing the ASCII art when starting up
                          ghostbusterV4.

  --json                  Only return a JSON object.
  --slackwebhook TEXT     Specify a Slack webhook URL to send notifications
                          about potential takeovers.

  --records PATH          Manually specify DNS records to check against.
                          ghostbusterV4 will check these IPs after checking
                          retrieved DNS records. See records.csv for an
                          example.

  --whitelist PATH        Specify filepath having list of IPs to whitelist

  --cloudflaretoken TEXT  Pull DNS records from Cloudflare, provide a CF API
                          token.

  --allregions            Run on all regions.
  --exclude TEXT          Comma delimited list of profile names to exclude.
  --regions TEXT          Comma delimited list of regions to run on.

  --help                  Show this message and exit.Example CommandsRun ghostbusterV4 with access to Cloudflare DNS records, send
notifications to a Slack webhook, iterate through every AWS profile
configured in.aws/config or .aws/credentialsfor all AWS regions❯ ghostbusterV4 scan aws --cloudflaretoken APIKEY --slackwebhook https://hooks.slack.com/services/KEY --allregionsRun ghostbusterV4 with a manually input list of subdomain A records (seerecords.csvin this repo for example file):❯ ghostbusterV4 scan aws --records records.csvYou can specify specific regions using--regionsset to a comma
delimited list of regions i.e.us-east-1,us-west-1.Example Output❯ ghostbusterV4 scan aws --cloudflaretoken whougonnacall
Obtaining all zone names from Cloudflare.
Obtaining DNS A records for all zones from Cloudflare.
Obtained 33 DNS A records so far.
Obtaining Route53 hosted zones for AWS profile: default.
Obtaining Route53 hosted zones for AWS profile: account-five.
Obtaining Route53 hosted zones for AWS profile: account-four.
Obtaining Route53 hosted zones for AWS profile: account-four-deploy.
Obtaining Route53 hosted zones for AWS profile: account-two-deploy.
Obtaining Route53 hosted zones for AWS profile: account-one-deploy.
Obtaining Route53 hosted zones for AWS profile: account-three-deploy.
Obtaining Route53 hosted zones for AWS profile: account-six.
Obtaining Route53 hosted zones for AWS profile: account-seven.
Obtaining Route53 hosted zones for AWS profile: account-one.
Obtained 124 DNS A records so far.
Obtaining EIPs for region: us-east-1, profile: default
Obtaining IPs for network interfaces for region: us-east-1, profile: default
Obtaining EIPs for region: us-east-1, profile: account-five
Obtaining IPs for network interfaces for region: us-east-1, profile: account-five
Obtaining EIPs for region: us-east-1, profile: account-four
Obtaining IPs for network interfaces for region: us-east-1, profile: account-four
Obtaining EIPs for region: us-east-1, profile: account-four-deploy
Obtaining IPs for network interfaces for region: us-east-1, profile: account-four-deploy
Obtaining EIPs for region: us-east-1, profile: account-two-deploy
Obtaining IPs for network interfaces for region: us-east-1, profile: account-two-deploy
Obtaining EIPs for region: us-east-1, profile: account-one-deploy
Obtaining IPs for network interfaces for region: us-east-1, profile: account-one-deploy
Obtaining EIPs for region: us-east-1, profile: account-three-deploy
Obtaining IPs for network interfaces for region: us-east-1, profile: account-three-deploy
Obtaining EIPs for region: us-east-1, profile: account-six
Obtaining IPs for network interfaces for region: us-east-1, profile: account-six
Obtaining EIPs for region: us-east-1, profile: account-seven
Obtaining IPs for network interfaces for region: us-east-1, profile: account-seven
Obtaining EIPs for region: us-east-1, profile: account-one
Obtaining IPs for network interfaces for region: us-east-1, profile: account-one
Obtained 415 unique elastic IPs from AWS.


Takeover possible: {'name': 'takeover.assetnotecloud.com', 'records': ['52.54.24.193']}Setting up your AWS accountsThe first step is creating keys or roles in your AWS accounts that grant
the privileges necessary to read Route53 records and describe elastic
addresses and EC2 network interfaces.To create a new IAM user in AWS, visit the following URL:https://console.aws.amazon.com/iam/home#/users$new?step=detailsChooseAccess key - Programmatic accessonly, and clickNext: Permissions.ClickAttach existing policies directlyand then clickCreate policy.ClickJSONand then paste in the following policy:{"Version":"2012-10-17","Statement":[{"Sid":"ghostbusterV4Policy","Effect":"Allow","Action":["ec2:DescribeAddresses","ec2:DescribeNetworkInterfaces","route53:ListResourceRecordSets","route53:ListHostedZonesByName","route53:GetTrafficPolicyInstance","route53:GetTrafficPolicy"],"Resource":"*"}]}ClickNext: Tagsand thenNext: Review.Set the name of the policy to beghostbusterV4Policy.ClickCreate Policy.Go tohttps://console.aws.amazon.com/iam/home#/users$new?step=permissions&accessKey&userNames=ghostbusterV4&permissionType=policiesSelectghostbusterV4Policy.ClickNext: Tagsand thenNext: Review.Click onCreate userand setup the AWS credentials in your.aws/credentialsfile.Repeat the above steps for each AWS account you own.This tool will work with however you’ve setup your AWS configuration
(multiple keys, or cross-account assume role profiles). This is managed
by boto3, the library used to interface with AWS.An example configuration looks like this:.aws/credentials:[default]
aws_access_key_id = AKIAIII...
aws_secret_access_key = faAaAaA....aws/config:[default]
output = table
region = us-east-1

[profile account-one]
role_arn = arn:aws:iam::911111111113:role/Ec2Route53Access
source_profile = default
region = us-east-1

[profile account-two]
role_arn = arn:aws:iam::911111111112:role/Ec2Route53Access
source_profile = default
region = us-east-1

[profile account-three]
region = us-east-1
role_arn = arn:aws:iam::911111111111:role/Ec2Route53Access
source_profile = defaultAlternatively, instead of having roles which are assumed, you can also
configure the.aws/credentialsfile to have a list of profiles and
assocaited keys with scoped access.Once your AWS configuration has been set with all the accounts in your
AWS environment, you can then run the tool using the following command:Setting up your AWS permissions for –rolesghostbusterV4 can use roles instead of profiles which removes the need of
having so many credentials at one place. However, roles approach will
require creating additional IAM policies within you organisation.Roles can be used via--rolesroles.csvor--autorolesflags. To
setup--rolesto work, one needs to create
ghostbusterV4TargetAccountRole rolenamed exactly like thatin every
account that is being scanned:{"Version":"2012-10-17","Statement":[{"Sid":"ghostbusterV4TargetAccountRole","Effect":"Allow","Action":["ec2:DescribeAddresses","ec2:DescribeNetworkInterfaces","route53:ListResourceRecordSets","route53:ListHostedZonesByName","route53:GetTrafficPolicyInstance","route53:GetTrafficPolicy"],"Resource":"*"}]}The ghostbusterV4 will be running in lambda/ec2/whatever withghostbusterV4role - let’s call it ghostbusterV4 master role. The master
role must be able to assume TargetAccountRoles.resource"aws_iam_policy""ghostbusterV4_target_account_roles"{name="ghostbusterV4_target_account_roles"path="/"description="Allow inspecting DNS and elastic IP data."policy=jsonencode({"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":"sts:AssumeRole","Resource":["arn:aws:iam::*:role/ghostbusterV4TargetAccountRole"]}]})tags={Project="ghostbusterV4"}}Setting up your AWS permissions for –autorolesAutomatic account discovery requires additional permission compared to
–roles. After setting up –roles to work, consider adding following IAM
policy in an account that has organisation overview:{sid="BaseAccess"actions=["organizations:DescribeAccount","organizations:ListAccounts"]resources=["*"]effect="Allow"}}Then, in the account that is running ghostbusterV4, attach following
policy to ghostbusterV4 master role so it can assume the organisation
lookup role:{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":"sts:AssumeRole","Resource":["arn:aws:iam::ORG_LOOKUP_ACCOUNT_ID:role/ta-application-security-prd-ghostbusterV4-org-role"]}]}Don’t forget to replace ORG_LOOKUP_ACCOUNT_ID with actual account ID.Setting up Cloudflare (Optional)If you want ghostbusterV4 to pull in all the A records that you have set
in Cloudflare, you will have to setup an API token that can read zones.https://dash.cloudflare.com/profile/api-tokensSetup a Cloudflare API token like shown in the screenshot below:Once you have obtained this API token, make a note of it somewhere
(password manager). In order to use it with ghostbusterV4, pass it in via
thecloudflaretokenargument.AuthorsShubham Shah-Initial work-githubSee also the list ofcontributorswho participated in this project.LicenseGNU Affero General Public LicenseTesting ghostbusterV4sClone this repo.Install virtualenv usingpip3 install virtualenvCreate a virtual environment usingvirtualenv venvActivate virtual environment using. venv/bin/activateInstall ghostbusterV4 by going to root of repo.pip3 install--editable.Make your changes and run the ghostbusterV4 command.