View Full Version : Wireless Flaw a Danger to Laptops
ronjor
January 16th, 2006, 11:32 AM
-{ Quote: "Laptops powered by Windows XP or Windows 2000 with built-in wireless capabilities (these includes most laptops on the market today) are configured so that when the user opens up the machine or turns it on, Windows looks for any available wireless connections. If the laptop cannot link up to a wireless network, it creates what's known as an ad-hoc "link local address," a supposed "private network" that assigns the wireless card a network address of 169.254.x.x (the Xs represent a random number between 1 and 254)" }-
Story (http://blogs.washingtonpost.com/securityfix/2006/01/windows_feature.html)
rdsu
January 16th, 2006, 12:23 PM
I observe that today with the ZoneAlarm Pro, but that network didn't appear on the Zones of ZAP... ???
FanJ
January 16th, 2006, 12:56 PM
Thread at DSLR:
http://www.dslreports.com/forum/remark,15254748
BugTraq:
http://www.securityfocus.com/archive/1/421868/30/0/threaded
rdsu
January 16th, 2006, 01:11 PM
-{ Quote: "Thread at DSLR:
http://www.dslreports.com/forum/remark,15254748
BugTraq:
http://www.securityfocus.com/archive/1/421868/30/0/threaded" }-
Thanks ;)
Cscampxp
January 16th, 2006, 01:37 PM
It's part of the Windows boot up process so it's not just laptops. When you have a NIC card installed one of the things your pc does before windows loads is what is called DHCP discover...it looks for DHCP servers and asks them for an ip address. If you you have a DHCP server (a router for example) the router responds back and gives (assigns) you an ip address (you then get a 192.168.0.x for example). But if it can't find a DHCP server or lets say the DHCP server is down, your pc will "automcatically" assign itself a 169.254.x.x ip address. It's called APIPA...Automatic Private IP Addressing
It does that whether you're wireless or not. If you're on wireless...that's right it will look for Wifi networks but won't automatically connect to it unless it your own default connection. It simply says that these are the available networks.
ronjor
January 18th, 2006, 03:44 PM
Windows Wi-Fi patch could be long time coming
-{ Quote: "Microsoft has confirmed that there is a Wi-Fi security vulnerability in Windows XP, but it may not be fixed for as long as 18 months." }-
Story (http://news.zdnet.com/2100-1009_22-6028275.html)
securityx
January 18th, 2006, 06:02 PM
Before everyone panics, take note of this paragraph:
"Anyway, you might be wondering now how you can make sure your Windows laptop is protected from this.....er, feature. First of all, if you are running any kind of network firewall -- including the firewall that comes built in to Windows XP -- you won't have to worry about some stranger connecting to your laptop. In fact, I had to shut down my firewall for both of us to successfully conduct our test."
Mrkvonic
January 19th, 2006, 04:40 AM
Hi,
Furthermore, you can assign static ips to machines and block dhcp.
Mrk
trickyricky
January 19th, 2006, 06:51 AM
Or do what I've done and use a separate app to control your wireless connection, which usually comes free with the wireless network adaptor and which doesn't have this problem.
Cscampxp
January 19th, 2006, 06:19 PM
In the NIC card's tcp/ip properties -----> alternate configuration tab
you can use a user configured "static" entry instead of it automatically defaulting to APIPA.
vBulletin® Copyright ©2000-2012, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2012, Wilders Security Forums