Hacker Uses XSS and Google Street View Data to Determine Physical Location
1–10 of 33 posts
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#2Lesson: Put a password on your router.
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#3Lesson: Put a password on your router.
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 Physical Location
#4Not to downplay a rather interesting vulnerability, but why does it matter if someone figures out where you are?
As much as I love my own real (not internet) privacy, I don't depend on people not knowing where I am. The success of sites such as Foursquare lead me to believe a large amount of people feel the same way.
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#5Very clever. What if you used the same attack to modify the router's iptables and open a port to the outside world. Upload some patched firmware and you now have the worlds largest botnet.
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#6Not to downplay a rather interesting vulnerability, but why does it matter if someone figures out where you are? As much as I love my own real (not internet) privacy, I don't depend on people not knowing where I am. The success of sites such as Foursquare lead me to believe a large amount of people feel the same way.
Furthermore, if you've got control of the router (and thus DNS server settings...) the user has much bigger problems: http://www.schneier.com/blog/archives/2007/02/driveby_pharmi...
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#7Not to downplay a rather interesting vulnerability, but why does it matter if someone figures out where you are? As much as I love my own real (not internet) privacy, I don't depend on people not knowing where I am. The success of sites such as Foursquare lead me to believe a large amount of people feel the same way.
Furthermore, if you've got control of the router (and thus DNS server settings...) the user has much bigger problems: http://www.schneier.com/blog/archives/2007/02/driveby_pharmi...
I don't think that he obtained control of the router, the article only states that he managed to get the router's mac address and the crossed referenced this with Google's wifi database(I assume). He can't modify the router just get a routing table from the compute somehow. At least that's what I understand from this extremely sparse in detail article.
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#8Earlier quoted context omitted.
Furthermore, if you've got control of the router (and thus DNS server settings...) the user has much bigger problems: http://www.schneier.com/blog/archives/2007/02/driveby_pharmi...
I don't think that he obtained control of the router, the article only states that he managed to get the router's mac address and the crossed referenced this with Google's wifi database(I assume). He can't modify the router just get a routing table from the compute somehow. At least that's what I understand from this extremely sparse in detail article.
He does have control of the router's settings (possibly even the ability to update the firmware with a malicious replacement?). Most routers let you set the DNS server addresses to be provided via DHCP. If you control DNS, you control which addresses domains resolve to. No need to control the routing table.
SSL helps mitigate the damage to some extent, but only if the site uses SSL.
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#9Earlier quoted context omitted.
I don't think that he obtained control of the router, the article only states that he managed to get the router's mac address and the crossed referenced this with Google's wifi database(I assume). He can't modify the router just get a routing table from the compute somehow. At least that's what I understand from this extremely sparse in detail article.
He does have control of the router's settings (possibly even the ability to update the firmware with a malicious replacement?). Most routers let you set the DNS server addresses to be provided via DHCP. If you control DNS, you control which addresses domains resolve to. No need to control the routing table. SSL helps mitigate the damage to some extent, but only if the site uses SSL.
Wait where does it state he he gained access to router? You can get the mac address of your router with sending a http request to it. Mine states it on the homepage. Doesn't mean you can change anything on there. What I'd like to know is how he manages to send this request, javascript origination policy should be blocking this.
EDIT: I was referring to the original article, schneier has a point, if the users has the default password set then yes he can login, but how is that even possible on most browsers today which prevents you from sending ajax request to anything but the original server?
EDIT2: Just tried it and got a error from chrome: 400 Bad Request Cross Site Action detected!
Re: Hacker Uses XSS and Google Street View Data to Determine Physical Location
#10Lesson: Put a password on your router.
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.
Let's assume the users is on 192.168.50.0/24 can his attack figure that out?