75
0.0.0.0 Day - 18 Yr Old Vulnerability Let Attackers Bypass All Browser Security
(cybersecuritynews.com)
this post was submitted on 08 Aug 2024
75 points (98.7% liked)
Technology
37585 readers
305 users here now
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.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Seems like a TCP/IP stack issue rather than a browser issue... 0.0.0.0 is not supposed to be a valid address (in fact, no IPv4 address with
0as the first octet is a valid destination IP). The network stack should be dropping those packets.0.0.0.0is only valid in a few use cases. When listening for connections, it means "listen on all IPs". This is a placeholder that the OS handles - it doesn't literally use that IP. Also, it's used as the source address for packets where the system doesn't have an IP yet (eg for DHCP). That's it.Yeah, I just did a quick test in Python to do a tcp connection to "0.0.0.0" and it made a loopback connection, instead of returning an error as I would have expected.