@floofloof@lemmy.ca
link
fedilink
English
27
edit-2
1M

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

@Kissaki@beehaw.org
link
fedilink
English
16
edit-2
1M

notably

Windows is not impacted by this issue.

quoting the main, critical part:

  1. Under public domain (.com), the browser sent the request to 0.0.0.0.
  2. The dummy server is listening on 127.0.0.1 (only on the loopback interface, not on all network interfaces).
  3. The server on localhost receives the request, processes it, and sends the response.
  4. 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.

Create a post

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

  • 1 user online
  • 144 users / day
  • 275 users / week
  • 709 users / month
  • 2.87K users / 6 months
  • 1 subscriber
  • 3.09K Posts
  • 64.9K Comments
  • Modlog