3 ms·
Interesting! This said, isn't it the same kind of attack that a malicious router (on the route between the sender and the receiver) could run? I.e. exploiting
by palata 4y ago
Interesting!
This said, isn't it the same kind of attack that a malicious router (on the route between the sender and the receiver) could run? I.e. exploiting a plaintext connection?
It feels like using an encrypted connection like HTTPS prevents it, right?
- ibz 4y agoExactly! While such research is cool, I think this has been long solved using HTTPS everywhere. You simply can't trust the router. Without HTTPS, all you need is a honeypot router that acts as a man-in-the-middle, which is not that hard of a setup.
- cudgy 4y agoIf the bad actor is injecting malicious javascript over plain text http to the device, doesn’t that get around this? Or is it possible to force the target ios/android/etc device to only accept https packets?
- layer8 4y agoIf my understanding is correct, it means you can’t really use unencrypted protocols even within an intranet or home network when it is wifi-based, which is kind of a pain due to certificates, and for example DNS typically being unencrypted.
- jeroenhd 4y agoThis attack does require bypassing some network security already. It defeats client isolation but the attacker does need to be on the WiFi network already (according to https://github.com/vanhoefm/macstealer https://github.com/vanhoefm/macstealer). AP isolation is usually off for all but big hotspots in my experience. This will be a problem for people using AP isolation for preventing their IoT from connecting to other devices in their network, assuming their IoT is malicious, but other than that the risk seems to be mostly with professional/corporate networks.
- blincoln 4y agoThere are still plenty of cleartext HTTP connections from most devices. An attacker only needs one to build the rest of an attack off of, e.g. wait for the browser to request http://banners.some-ad-platform.com/12345.html http://banners.some-ad-platform.com/12345.html, spoof a response that redirects to http://<domain-to-execute-javascript-in>/xss.html http://<domain-to-execute-javascript-in>/xss.html, and then spoof the response to that second request with arbitrary JavaScript. There are other factors that can make it less exploitable for a specific attack, like HSTS being enabled for a specific site, but unless you have some kind of host-based firewall that blocks all outbound cleartext connections, there's probably some potential for exploitation.