68
0.0.0.0 Day - 18 Yr Old Vulnerability Let Attackers Bypass All Browser Security
(cybersecuritynews.com)
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.
I'm inclined to agree. This looks like a misunderstanding of RFC 5735.
From that RFC:
(note that it only says "source address")
which was based on RFC 1122, which states:
(section 3.3.6 just talks about it being a legacy IP for broadcasts - I don't think that even works any more)
Okay, I see where I went wrong. Thank you.
I don't think 0.0.0.0 works for broadcasts anymore, either - I think those get filtered by default these days.
I wasn't disagreeing with you :) or at least I think I wasn't. I was just quoting the RFC you linked to.