So you were said that everything belonging to some company is inside the scope, and you want to figure out what this company actually owns.
The goal of this phase is to obtain all the companies owned by the main company and then all the assets of these companies. To do so, we are going to:
Find the acquisitions of the main company, this will give us the companies inside the scope.
Find the ASN (if any) of each company, this will give us the IP ranges owned by each company
Use reverse whois lookups to search for other entries (organisation names, domains...) related to the first one (this can be done recursively)
Use other techniques like shodan
sslfilters to search for other assets (the
ssl trick can be done recursively).
First of all, we need to know which other companies are owned by the main company. One option is to visit https://www.crunchbase.com/, search for the main company, and click on "acquisitions". There you will see other companies acquired by the main one. Other option is to visit the Wikipedia page of the main company and search for acquisitions.
Ok, at this point you should know all the companies inside the scope. Lets figure out how to find their assets.
An autonomous system number (ASN) is a unique number assigned to an autonomous system (AS) by the Internet Assigned Numbers Authority (IANA). An AS consists of blocks of IP addresses which have a distinctly defined policy for accessing external networks and are administered by a single organisation but may be made up of several operators.
It's interesting to find if the company have assigned any ASN to find its IP ranges. It will be interested to perform a vulnerability test against all the hosts inside the scope and look for domains inside these IPs. You can search by company name, by IP or by domain in https://bgp.he.net/. Depending on the region of the company this links could be useful to gather more data: AFRINIC (Africa), Arin(North America), APNIC (Asia), LACNIC (Latin America), RIPE NCC (Europe). Anyway, probably all the useful information (IP ranges and Whois) appears already in the first link.
#You can try "automate" this with amass, but it's not very recommendedamass intel -org teslaamass intel -asn 8911,50313,394161
You can find the IP ranges of an organisation also using http://asnlookup.com/ (it has free API).
At this point we known all the assets inside the scope, so if you are allowed you could launch some vulnerability scanner (Nessus, OpenVAS) over all the hosts. Also, you could launch some port scans or use services like shodan to find open ports and depending on what you find you should take a look in this book to how to pentest several possible service running. Also, It could be worth it to mention that you can also prepare some default username and passwords lists and try to bruteforce services with https://github.com/x90skysn3k/brutespray.
We know all the companies inside the scope and their assets, it's time to find the domains inside the scope.
Please, note that in the following purposed techniques you can also find subdomains and that information shouldn't be underrated.
First of all you should look for the main domain(s) of each company. For example, for Tesla Inc. is going to be tesla.com.
As you have found all the IP ranges of the domains you could try to perform reverse dns lookups on those IPs to find more domains inside the scope. Try to use some dns server of the victim or some well-known dns server (22.214.171.124, 126.96.36.199)
dnsrecon -r <DNS Range> -n <IP_DNS> #DNS reverse of all of the addressesdnsrecon -d facebook.com -r 188.8.131.52/24 #Using facebooks dnsdnsrecon -r 184.108.40.206/24 -n 220.127.116.11 #Using cloudflares dnsdnsrecon -r 18.104.22.168/24 -n 22.214.171.124 #Using google dns
For this to work, the administrator has to enable manually the PTR. You can also use a online tool for this info: http://ptrarchive.com/
Inside a whois you can find a lot of interesting information like organisation name, address, emails, phone numbers... But which is even more interesting is that you can find more assets related to the company if you perform reverse whois lookups by any of those fields (for example other whois registries where the same email appears). You can use online tools like:
https://www.reversewhois.io/ - Free
https://www.whoxy.com/ - Free web, not free API.
http://reversewhois.domaintools.com/ - Not free
https://drs.whoisxmlapi.com/reverse-whois-search - Not Free (only 100 free searches)
https://www.domainiq.com/ - Not Free
Note that you can use this technique to discover more domain names every time you find a new domain.
If find the same ID of the same tracker in 2 different pages you can suppose that both pages are managed by the same team. For example, if you see the same Google Analytics ID or the same Adsense ID on several pages.
There are some pages that let you search by these trackers and more:
Note that you can use this technique to discover more domain names every time you find a new domain.
As you already know the name of the organisation owning the IP space. You can search by that data in shodan using:
org:"Tesla, Inc." Check the found hosts for new unexpected domains in the TLS certificate.
You could access the TLS certificate of the main web page, obtain the Organisation name and then search for that name inside the TLS certificates of all the web pages known by shodan with the filter :
Go to the main page an find something that identifies the company, like the copyright ("Tesla © 2020"). Search for that in google or other browsers to find possible new domains/pages.
Assetfinder is a tool that look for domains related with a main domain and subdomains of them, pretty amazing.
Check for some domain takeover. Maybe some company is using some a domain but they lost the ownership. Just register it (if cheap enough) and let know the company.
If you find any domain with an IP different from the ones you already found in the assets discovery, you should perform a basic vulnerability scan (using Nessus or OpenVAS) and some port scan with nmap/masscan/shodan. Depending on which services are running you can find in this book some tricks to "attack" them. Note that sometimes the domain is hosted inside an IP that is not controlled by the client, so it's not in the scope, be careful.
We know all the companies inside the scope, all the assets of each company and all the domains related to the companies.
It's time to find all the possible subdomains of each found domain.
Let's try to get subdomains from the DNS records. We should also try for Zone Transfer (If vulnerable, you should report it).
dnsrecon -a -d tesla.com
The fastest way to obtain a lot of subdomains is search in external sources. I'm not going to discuss which sources are the bests and how to use them, but you can find here several utilities: https://pentester.land/cheatsheets/2018/11/14/subdomains-enumeration-cheatsheet.html
The most used tools are Amass, subfinder, findomain, OneForAll, assetfinder and Subvenkon, I would recommend to start using them configuring the API keys, and then start testing other tools or possibilities.
amass enum [-active] [-ip] -d tesla.com./subfinder-linux-amd64 -d tesla.com [-silent]./findomain-linux -t tesla.com [--quiet]python3 oneforall.py --target tesla.com [--dns False] [--req False] runassetfinder --subs-only <domain>
Another possibly interesting tool is gau. It fetches known URLs from AlienVault's Open Threat Exchange, the Wayback Machine, and Common Crawl for any given domain.
This project offers for free all the subdomains related to bug-bounty programs. You can access this data also using chaospy or even access the scope used by this project https://github.com/projectdiscovery/chaos-public-program-list
Let's try to find new subdomains brute-forcing DNS servers using possible subdomain names. The most recommended tools for this are massdns, gobuster, aiodnsbrute and shuffledns. The first one is faster but more prone to errors (you should always check for false positives) and the second one is more reliable (always use gobuster).
For this action you will need some common subdomains lists like:
For massdns you will need to pass as argument the file will all the possible well formed subdomains you want to bruteforce:
sed 's/$/.domain.com/' subdomains.txt > bf-subdomains.txt./massdns -r resolvers.txt -w /tmp/results.txt bf-subdomains.txtgrep -E "tesla.com. [0-9]+ IN A .+" /tmp/results.txt
Gobuster bruteforcing dnsgobuster dns -d mysite.com -t 50 -w subdomains.txt
You can find some VHosts in IPs using HostHunter
If you suspect that some subdomain can be hidden in a web server you could try to brute force it:
gobuster vhost -u https://mysite.com -t 50 -w subdomains.txtwfuzz -c -w /usr/share/wordlists/SecLists/Discovery/DNS/subdomains-top1million-20000.txt --hc 400,404,403 -H "Host: FUZZ.example.com" -u http://example.com -t 100#From https://github.com/allyshka/vhostbrutevhostbrute.py --url="example.com" --remoteip="10.1.1.15" --base="www.example.com" --vhosts="vhosts_full.list"
While looking for subdomains keep an eye to see if it is pointing to any type of bucket, and in that case check the permissions. Also, as at this point you will know all the domains inside the scope, try to brute force possible bucket names and check the permissions.
If you find any subdomain with an IP different from the ones you already found in the assets discovery, you should perform a basic vulnerability scan (using Nessus or OpenVAS) and some port scan with nmap/masscan/shodan. Depending on which services are running you can find in this book some tricks to "attack" them. Note that sometimes the subdomain is hosted inside an IP that is not controlled by the client, so it's not in the scope, be careful.
We have found all the companies and their assets and we know IP ranges, domains and subdomains inside the scope. It's time to search for web servers.
In the previous steps probably you have already perform some recon to the IPs and domains discovered, so you may already found all the possible web servers. However, if you haven't we are now going to see some fast tricks to search for web servers inside the scope.
Please, note that this will be oriented to search for web apps, you should perform the vulnerability and port scanning also (if allowed by the scope).
A fast method to discover ports open related to web servers using masscan can be found here. Another friendly tool to look for web servers is httprobe and fprobe. You just pass a list of domains and it will try to connect to port 80 (http) and 443 (https). You can additional indicate to try other ports:
cat /tmp/domains.txt | httprobe #Test all domains inside the file for port 80 and 443cat /tmp/domains.txt | httprobe -p http:8080 -p https:8443 #Check port 80, 443 and 8080 and 8443
Now that you have discovered all the web servers running in the scope (in IPs of the company and all the domains and subdomains) you probably don't know where to start. So, let's make it simple and start just taking screenshots of all of them. Just taking a look to the main page of all of them you could find weird endpoints more prone to be vulnerable.
Congratulations! At this point you have already perform all the basic enumeration. Yes, it's basic because a lot more enumeration can be done (will see more tricks later). Do you know that the BBs experts recommends to spend only 10-15mins in this phase? But don't worry, one you have practice you will do this even faster than that.
So you have already:
Found all the companies inside the scope
Found all the assets belonging to the companies (and perform some vuln scan if in scope)
Found all the domains belonging to the companies
Found all the subdomains of the domains (any subdomain takeover?)
Found all the web servers and took a screenshot of them (anything weird worth a deeper look?)
Then, it's time for the real Bug Bounty hunt! In this methodology I'm not going to talk about how to scan hosts (you can see a guide for that here), how to use tools like Nessus or OpenVas to perform a vuln scan or how to look for vulnerabilities in the services open (this book already contains tons of information about possible vulnerabilities on a lot of common services). But, don't forget that if the scope allows it, you should give it a try.
Now that we have built the list of assets of our scope it's time to search for some OSINT low-hanging fruits.
Anyway, the majority of the vulnerabilities found by bug hunters resides inside web applications, so at this point I would like to talk about a web application testing methodology, and you can find this information here.
Congratulations! The testing has finished! I hope you have find some vulnerabilities.
At this point you should have already read the Pentesting Web Methodology and applied it to the scope. As you can see there is a lot of different vulnerabilities to search for.
If you have find any vulnerability thanks to this book, please reference the book in your write-up.