News for hackers. Stuff that matters.
Re:Hacker Uses XSS and Google Street View Data to Determine ... by CytokineStorm on Saturday August 14, 2010 @11:53PM (#1604553)
Or even better, change the default IP address for the admin login. This attack relies on a bunch of hidden iframes loading IPs that are common default addresses of the admin login page.
Re:Hacker Uses XSS and Google Street View Data to Determine ... by marcinw on Sunday August 15, 2010 @02:21AM (#1604696)
How's that better? That's like changing the port SSH listens on to 2222 even though root's password is "root".
Re:Hacker Uses XSS and Google Street View Data to Determine ... by carussell on Sunday August 15, 2010 @01:56PM (#1605551)
Twice I've had routers notify me that 192.168.0.1 is in use by another network service and automatically remap its own services to 10.0.0.x. One of these times was due to a DSL modem's web administration being on 192.168.0.1.
Re:Hacker Uses XSS and Google Street View Data to Determine ... by nkassis on Sunday August 15, 2010 @01:17AM (#1604652)
Let's assume the users is on 192.168.50.0/24 can his attack figure that out?
Re:Hacker Uses XSS and Google Street View Data to Determine ... by woodall on Sunday August 15, 2010 @02:03AM (#1604686)
The attack/code he showed cannot, but what you can do it write different iframes. Here is an example:

a+'.'+b+'.'+c+'.'+d

where a=192 b=168 c=0-255 b=0-255

Of course this could be any private network address range[1]. Next you would use document.write or .innertext to make these iframes. Personally I wouldn't stop at the first one. I would log all the frames that loaded into an array and from there test them further. I would also get the users IP address and tack on :80, :8080, :21, ect and see what I am presented with- web torrent frontends, ftp servers, ect.

[1] http://en.wikipedia.org/wiki/Private_network

Re:Hacker Uses XSS and Google Street View Data to Determine ... by bnchdrff on Sunday August 15, 2010 @10:33AM (#1605187)
This will take forever, and also make the user's browser unresponsive.

for(var c=0;i<255;i++) { for (var d=0;j<255;j++) { document.write('<iframe height="1" width="1" src="http://192.168. + c + '.' + d + '" id="' + i + '.' + j + '" name="' + c + '.' + d + '"></iframe>'); } }

<iframe> portscans, wow.

For a massively-deployed hack like Samy's, it makes plenty of sense to just check the small handful of major-brand wifi routers.

Re:Hacker Uses XSS and Google Street View Data to Determine ... by woodall on Sunday August 15, 2010 @02:20PM (#1605586)
I totally agree. You should only be checking for routers that have known vulnerabilities, but was not the initial question.