Re:“We are considering adding an extension to restrict the u...
by jnbiche on Tuesday July 28, 2015 @07:05AM
(#9960634)
Can you expand on this, please? How does it make it easier to XSS?
[ Parent
| on HN ]
Re:“We are considering adding an extension to restrict the u...
by chadrs on Tuesday July 28, 2015 @07:19AM
(#9960670)
Well, I'm not sure about XSS, but imagine you know someone's home IP is:
192.168.1.10
Based on this, you can probably guess the router is 192.168.1.1 and maybe even have a clue about the vendor based on the IP assigning patterns.
Then you can direct them to a page with an submitting POST <form> that makes modifications to their router settings. This is more like CSRF than XSS though.
Re:“We are considering adding an extension to restrict the u...
by malka on Tuesday July 28, 2015 @08:37AM
(#9960971)
funny, of all the routers I used (all were provided by my ISP), their IP were 192.168.1.254
Re:“We are considering adding an extension to restrict the u...
by pjc50 on Tuesday July 28, 2015 @07:18AM
(#9960668)
Previously you'd have to guess that the router was on 192.168.x.1. http://www.gironsec.com/blog/2015/01/owning_modems_and_route...
Re:“We are considering adding an extension to restrict the u...
by milankragujevic on Tuesday July 28, 2015 @07:40AM
(#9960743)
It doesn't. All major browsers block connections to 192.168.XX.XX (and any other externally unroutable IP) from external (http on the Web, not localhost) web pages.