← home

A "playbook" for CTF purposes

Pipeline

Network Mapping

See nmap.md for more details.

First, we want to find our IP address: ip addr show. You already know how to interpret network controllers. Find your IP address. If your IP address has a /16 you're on a bigger network, and /24 if you're on a smaller network.

To do more broad network discovery, run:

To do discovery via an arp scan, do:

Now, we have some IP addresses to play with! Here are some general notes regarding nmap:

Timing templates:

Classical ports:

You can confirm individual connection things with netcat:

Things you might run into when scanning:

Some other useful tools for further enumeration:

Using DNS...

Using DNS, we can get a ton of different information on a network. First, how do we obtain what server is a DNS server?

Once we have the IP of the server sending dns requests, we can try a few things:

What to do now with all this info?

Okay, we found some random shit. We did some discovering. What now? Well, we really have two options...

Nice tools

Crackmapexec

a "swiss army knife" for pen testing networks. See: github.com/byt3bl33d3r/CrackMapExec.

This tool is mostly used for password stuff and brute forcing. This is good for SMB (fucking windows), LDAP (directory access), WINRM, MSSQL, SSH, FTP, RDP, WMI

Other Tools for merking shit you find

Priv escalation

← home