Subdomain Takeover

OWASP: WSTG-CONF-10

Theory

A subdomain takeover occurs when an attacker gains control over a subdomain of a target domain. Typically, this happens when the victim’s external DNS server subdomain record is configured to point to a non-existing or non-active resource/external service/endpoint.

If the subdomain takeover is successful, a wide variety of attacks are possible (serving malicious content, phishing, stealing user session cookies, credentials, etc.). This vulnerability could be exploited for a wide variety of DNS resource records including: A, CNAME, MX, NS, TXT etc. In terms of the attack severity, an NS subdomain takeover (although less likely) has the highest impact, because a successful attack could result in full control over the whole DNS zone and the victim’s domain.

Practice

Enumerate

Before attempting a domain or subdomain takeover, it's crucial to enumerate all subdomains associated with the target domain. Refer to the below section for comprehensive techniques and tools.

Subdomains enumeration

Scanning for Subdomain Takeover

After enumerating subdomains, we can use these tools to perform a Subdomain Takeover scan and detect any subdomains that might be vulnerable.

Subzy (Golang) is a subdomain takeover vulnerability checker which works based on matching response fingerprints from can-i-take-over-xyz.

We can use this tools and scan for each subdomain discovered.

# Scan a list of subdomains
subzy run --targets domains.txt

# Scan for a single subdomain
subzy run --target test.example.com

# One-liner: find subdmains + scan for domain takeover
echo 'example.com'|(subfinder -all||assetfinder -subs-only)|uniq -u > domains.txt;subzy r --targets domains.txt | sed 's/\x1b\[[0-9;]*m//g' |grep -iE -A 2 "\[ VULNERABLE"

We may use httpx for checking HTTP response status for each subdomain discovered.

# -title: Display page title
# -wc: Display response body word count
# -sc: Display response status-code
# -cl: Display response content-length
# -ct: Display response content-type
# -location: Display response redirect location
# -web-server: Display server name
# -asn: Display host ASN information
# -o: Output
cat domains.txt | httpx -title -wc -sc -cl -ct -location -web-server -asn -o alive-subdomains.txt

# Resume Scan (-resume)
# You can resume the scan using `resume.cfg`.
cat domains.txt | httpx -title -wc -sc -cl -ct -location -web-server -asn -o alive-subdomains.txt -resume resume.cfg

The, we can then check for error codes 404 and check on can-i-take-over-xyz if the provider allows us to register subdomains.

Subdover (python) is a subdomain takeover vulnerability scanner, which has more than 88+ fingerprints of potentially vulnerable services.

# From list
python3 subdover.py -l domains.txt

# Single domain (will scan for subdomains using findomain)
python3 subdover.py -d example.com

mx-takeover focuses DNS MX records and detects misconfigured MX records. It currently support three technique. These are,

MX domains that will expire soon
Unregistered MX domains
Domains that points to not currently in use by mailgun.

cat domains.txt| mx-takeover -mailgun-api <API-KEY> -check-whois -w 64

Subdomain Takeover

Identify Misconfigurations for Subdomains

First, check DNS records for identifying what’s on the destination of the subdomain.

dig sub.example.com ANY
dig sub.example.com CNAME

If the HEADER status is NXDOMAIN error in the result, subdomain takeover might be possible. Also we can try to access them with web browser or command-line:

# -L: Follow redirect
# -v: Verbose mode
curl -Lv app.example.com
curl -v cloud.example.com
curl -v mail.example.com

Spoof with the Subdomain

If a certain subdomain can be accessible but the error page of the specific provider (e.g. GitHub, Google Cloud, Wix, etc.) appeared, it means that the subdomain of the settings in the service provider was removed but the DNS record (e.g. A, CNAME) remains yet.

In short, attackers can spoof as a legitimate site by claiming this subdomain in the provider.

Here’s an abstract example:

Login the target provider.
Create a malicious website.
Add the target subdomain (e.g. app.example.com) as custom domain in the setting page.
If users visit app.example.com, they have now visited a malicious website created by an attacker.

It’s more dangerous If NS record is vulnerable because if the nameserver is taken over, an attacker can take full control of victim’s domains.

To gather NS records for the target domain, use dig command.

dig example.com +short NS

# Result examples
ns-100.abcde.org
ns-120.abcde.co.uk

Next, check if the gathered domains can be purchased with domain name registrar like GoDaddy, NameCheap.

For example, search [abcde.org](http://abcde.org) in the domain search page of NameCheap. If this domain can be purchased, attackers can buy this domain then take control the name resolution of a victim by creating the custom nameserver which pointed to this domain.

Resources

WSTG - Latest | OWASP Foundationowasp.org

Subdomain takeover - Security | MDNMDN Web Docs

Domain/Subdomain takeover - HackTricksHackTricks

Introduction - Exploit Notesexploit-notes.hdks.org

Last updated 1 year ago