3 ms·
Before actually testing this with the real payload, is there a better way of determining if you have a potentially vulnerable driver than something like this?
by elasticdog 14y ago
Before actually testing this with the real payload, is there a better way of determining if you have a potentially vulnerable driver than something like this?
# awk '/eth/ { print $1 }' <(ifconfig -a) | cut -d':' -f1 | uniq | while read interface; do echo -n "$interface "; ethtool -i $interface | grep driver; done
eth0 driver: e1000e
eth1 driver: e1000e
- minaguib 14y agoThis is not about the particular linux driver, but about a particular chipset, and even then, only sometimes... The linux e1000e may support many chipsets, so the fact that it's in service on your box doesn't necessarily mean you're running the suspect chipset, or that it's vulnerable. Check with lspci -v, and check with the concrete test using the cold boot+magic packet others and the OP have posted.