text stringlengths 0 1.99k |
|---|
[0] http://ha.ckers.org/fierce/ |
For an example let's take Blackwater. We start out knowing their homepage is at |
academi.com. Running fierce.pl -dns academi.com we find the subdomains: |
67.238.84.228 email.academi.com |
67.238.84.242 extranet.academi.com |
67.238.84.240 mail.academi.com |
67.238.84.230 secure.academi.com |
67.238.84.227 vault.academi.com |
54.243.51.249 www.academi.com |
Now we do whois lookups and find the homepage of www.academi.com is hosted on |
Amazon Web Service, while the other IPs are in the range: |
NetRange: 67.238.84.224 - 67.238.84.255 |
CIDR: 67.238.84.224/27 |
CustName: Blackwater USA |
Address: 850 Puddin Ridge Rd |
Doing a whois lookup on academi.com reveals it's also registered to the same |
address, so we'll use that as a string to search with for the reverse whois |
lookups. As far as I know all the actual reverse whois lookup services cost |
money, so I just cheat with google: |
"850 Puddin Ridge Rd" inurl:ip-address-lookup |
"850 Puddin Ridge Rd" inurl:domaintools |
Now run fierce.pl -range on the IP ranges you find to lookup dns names, and |
fierce.pl -dns on the domain names to find subdomains and IP addresses. Do more |
whois lookups and repeat the process until you've found everything. |
Also just google the organization and browse around its websites. For example on |
academi.com we find links to a careers portal, an online store, and an employee |
resources page, so now we have some more: |
54.236.143.203 careers.academi.com |
67.132.195.12 academiproshop.com |
67.238.84.236 te.academi.com |
67.238.84.238 property.academi.com |
67.238.84.241 teams.academi.com |
If you repeat the whois lookups and such you'll find academiproshop.com seems to |
not be hosted or maintained by Blackwater, so scratch that off the list of |
interesting IPs/domains. |
In the case of FinFisher what led me to the vulnerable finsupport.finfisher.com |
was simply a whois lookup of finfisher.com which found it registered to the name |
"FinFisher GmbH". Googling for: |
"FinFisher GmbH" inurl:domaintools |
finds gamma-international.de, which redirects to finsupport.finfisher.com |
...so now you've got some idea how I map out a target. |
This is actually one of the most important parts, as the larger the attack |
surface that you are able to map out, the easier it will be to find a hole |
somewhere in it. |
--[ 4 ]-- Scanning & Exploiting |
Scan all the IP ranges you found with nmap to find all services running. Aside |
from a standard port scan, scanning for SNMP is underrated. |
Now for each service you find running: |
1) Is it exposing something it shouldn't? Sometimes companies will have services |
running that require no authentication and just assume it's safe because the url |
or IP to access it isn't public. Maybe fierce found a git subdomain and you can |
go to git.companyname.come/gitweb/ and browse their source code. |
2) Is it horribly misconfigured? Maybe they have an ftp server that allows |
anonymous read or write access to an important directory. Maybe they have a |
database server with a blank admin password (lol stratfor). Maybe their embedded |
devices (VOIP boxes, IP Cameras, routers etc) are using the manufacturer's |
default password. |
3) Is it running an old version of software vulnerable to a public exploit? |
Webservers deserve their own category. For any webservers, including ones nmap |
will often find running on nonstandard ports, I usually: |
1) Browse them. Especially on subdomains that fierce finds which aren't intended |
for public viewing like test.company.com or dev.company.com you'll often find |
interesting stuff just by looking at them. |
2) Run nikto [0]. This will check for things like webserver/.svn/, |
webserver/backup/, webserver/phpinfo.php, and a few thousand other common |
mistakes and misconfigurations. |
3) Identify what software is being used on the website. WhatWeb is useful [1] |
4) Depending on what software the website is running, use more specific tools |
like wpscan [2], CMS-Explorer [3], and Joomscan [4]. |
First try that against all services to see if any have a misconfiguration, |
publicly known vulnerability, or other easy way in. If not, it's time to move |
on to finding a new vulnerability: |
5) Custom coded web apps are more fertile ground for bugs than large widely used |
projects, so try those first. I use ZAP [5], and some combination of its |
automated tests along with manually poking around with the help of its |
intercepting proxy. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.