2 ms·
Maybe I‘m lacking the imagination for truly nefarious things, but what would be the problem with raw socket access in the browser? Modern browsers can already
by lxgr 4y ago
Maybe I‘m lacking the imagination for truly nefarious things, but what would be the problem with raw socket access in the browser?
Modern browsers can already communicate peer to peer (via WebRTC) and DDoS other web servers (via CORS failures or good old embedding).
Is the main concern the increased attack opportunity of non-web servers?
- justinclift 4y agoThe ad industry would surely figure out some way to load stuff for fingerprinting / user tracking with it. :(
- ec109685 4y agoBrowser can’t mediate raw socket connections.
- kevingadd 4y agoYou can use raw sockets to exploit vulnerabilities in arbitrary devices on the user's local network, like routers and IoT devices, which frequently have fixed default IPs
- bawolff 4y agoYou can already do that with svgs (in many cases not all). Although recently browsers changed rules for connecting to internal ips
- Matheus28 4y agoYes but also web servers. You could make requests to them (although you wouldn’t have access to the user cookies) and bypass CORS. There’s some more details in the WebSocket RFC for why it’s a bad idea to give access to tcp/udp sockets to untrusted code unless the receiving server is willing to receive them.
- lxgr 4y agoWithout cookies, is that really a problem though? You can already cause OPTION requests, if the concern is denial of service (although these are presumably much easier to filter out at a load balancer or similar than arbitrary unauthenticated requests).