3 ms·
They're only attacking host-lookup, so you just have to worry about people who can connect to your service and are able to control name server response. This me
by peterwwillis 12y ago
They're only attacking host-lookup, so you just have to worry about people who can connect to your service and are able to control name server response. This means your network services that are internet-accessible. Everything else can wait for a maintenance window for the reboot.
~# netstat -lnp | grep -e "\(tcp.*LISTEN\|udp\)" | cut -d / -f 2- | sort -u
cupsd
dnsmasq
httpd
nmbd
ntpd
qemu-kvm
rpc.portmap
rpc.statd
sendmail: acce
smbd
ssh
sshd
- correxion 12y agosudo netstat -lnp | awk -F/ '/LISTEN /{print $2}'
- jerematasno 12y agoIt doesn't have to be internet accessible, AFAIK. If an attacker can get something to do arbitrary DNS lookups, I think it can be attacked. For instance, monitoring/log correlation software might be vulnerable.
- NickNameNick 12y agoIf you have backend systems parsing XML, then an XXE[1] attack could trigger a DNS lookup, for example. [1]https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing https://www.owasp.org/index.php/XML_External_Entity_%28XXE%2...
- sarciszewski 12y agoOoh, that could lead to some very interesting attack vectors. :D