The article literally doesn’t explain the vulnerability at all.
It keeps promising to, then goes off into more ChatGPT-style rambling. It’s a bad article. This one is more informative:
https://www.oligo.security/blog/0-0-0-0-day-exploiting-localhost-apis-from-the-browser
notably
Windows is not impacted by this issue.
quoting the main, critical part:
- Under public domain (.com), the browser sent the request to 0.0.0.0.
- The dummy server is listening on 127.0.0.1 (only on the loopback interface, not on all network interfaces).
- The server on localhost receives the request, processes it, and sends the response.
- The browser blocks the response content from propagating to Javascript due to CORS.
This means public websites can access any open port on your host, without the ability to see the response.
Everybody who could explain it well is at Hacker Summer Camp right now.
I didn’t realize DEFCON was this weekend already, but this is a solid point 😂
Welp, I guess sandboxing a browser that has a sandbox might still be a good idea
hunter2 Wow it works!
Yes! Another huge win for links2gang !links2@lemmy.sdf.org
