Jeff, I'll start a list. Others can add to it. Session hijacking (Man in the middle attack) Malicious Web sites (From spyware to activeX and Java) Any email, ftp, tftp, or http download (Trojaned, wormed, virused) eDonkey, Morpheous, Kazaa (File sharing, but whats the file you are sharing. Someone has remote access to system)
Nat hides you... poorly. They don't need your IP to ennumerate you, if your system answers. Anti-virus. Backups. Firewalls. Backups. IDS. Backups. ---ids---nat---ids---systems = okay break up large networks into security domains, separated by ids's, firewalls, connected with tunnels, ipsec over vpn, ssh, etc. Google any of the above exploits/attacks. Fire the admin. Then backup. Then disable old admins account. Then backup. D. Weiss My system is safe. I never turn it on. -----Original Message----- From: Schuler, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 7:17 PM To: [EMAIL PROTECTED] Subject: Network Address Translation insecurities I am looking for information regarding the insecurities and vulnerabilities that exist in Network Address Translation. One of our admins feels that because everything is NAT'd that there is no way anyone can break into the systems that are NAT'd. I know that this is not a completely accurate statement but need to find some research and documentation regarding this. All our systems are behind at least one firewall so please don't advise me to install a firewall as extra security as they are already there. I just want to make sure that we are not overlooking serious vulnerabilities just because the box is behind a NAT. In order to justify doing vulnerability testing on some of our internal systems I need to demonstrate the insecurities in NAT. Thanks in advance Jeff Schuler
