Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

add well-known UDP-ports to scans and datasets #13

Open
zer010bs opened this issue Jun 17, 2019 · 3 comments
Open

add well-known UDP-ports to scans and datasets #13

zer010bs opened this issue Jun 17, 2019 · 3 comments

Comments

@zer010bs
Copy link

zer010bs commented Jun 17, 2019

SNMP: tcp and udp

161/162 (snmp, trap)
10161/10162 (snmps, trap)

if open -> bad
if open + communitystring is readable (like public) -> critical

impact: ability to read machine-data, configs (firewall, router 'n' stuff). if not secured,, ability to alter machine-settings

https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#Using_SNMP_to_attack_a_network

@zer010bs
Copy link
Author

zer010bs commented Jul 11, 2019

UDP: 632 / IPMI

@zer010bs zer010bs changed the title add well-known snmp-ports to scans and datasets add well-known UDP-ports to scans and datasets Jul 18, 2019
@zer010bs
Copy link
Author

zer010bs commented Jul 18, 2019

UDP:
389 / LDAP
636 / LDAPS

@Phenomite
Copy link

udp 5 Remote job entry
udp 11 systat
udp 15 netstat (systat sister)
udp 13 daytime no payload, returns 30 byte avg (2x amp)
udp 18 message send protocol
udp 37 time protocol (can enumerate system timezone, albiet IP basically does that already)
udp 39 resource location protocol
udp 54 Xerox (lots of open responders)
udp 629 netinfo for macOS
udp 631 Internet printing protocol
udp 639 MSDP
udp 1167 Cisco IP SLAs Control Protocol
udp 1723 pptp
udp 1883 MQTT
udp 2003 Dlink click-n-connect / Brutus
udp 3000 btsync
udp 2049 nfsd rpc
udp 4500 IPSec Nat traversal

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants