2 ms·
Where did the browser go wrong, here? They followed all security practices. The browser isn't what is running the payload. Unless, you're suggesting that nobod
by shakna 1y ago
Where did the browser go wrong, here? They followed all security practices. The browser isn't what is running the payload.
Unless, you're suggesting that nobody should be able to download programs, unless blessed by some large company?
- thwaysec 1y agoThe browser is allowing remote code to talk with 127.0.0.1
- shakna 1y agoRight... And that's only blocked in the host asks for it via CORS, or Same-Origin policies. Because otherwise you break any combination of apps. It's up to the server on the localhost not to blindly trust. And has been since the beginning.
- thwaysec 1y agoMight have been there since the beginning, but doesn't make it less surprising or bad. That's a _ridiculously_ bad thing to allow. Any website to talk with just about ANY port on your local machine. Incredible.