Comment on 0.0.0.0 Day - 18 Yr Old Vulnerability Let Attackers Bypass All Browser Security

dan@upvote.au ⁨1⁩ ⁨month⁩ ago

• drwho@beehaw.org ⁨1⁩ ⁨month⁩ ago

  I’m inclined to agree. This looks like a misunderstanding of RFC 5735.

  source

  • dan@upvote.au ⁨1⁩ ⁨month⁩ ago

    which was based on RFC 1122, which states:

                We now summarize the important special cases for Class A, B,
                and C IP addresses, using the following notation for an IP
                address:
    
                    { <Network-number>, <Host-number> }
    
                or
                    { <Network-number>, <Subnet-number>, <Host-number> }
    
                and the notation "-1" for a field that contains all 1 bits.
                This notation is not intended to imply that the 1-bits in an
                address mask need be contiguous.
    ...
                (a)  { 0, 0 }
    
                     This host on this network.  MUST NOT be sent, except as
                     a source address as part of an initialization procedure
                     by which the host learns its own IP address.
    
                     See also Section 3.3.6 for a non-standard use of {0,0}.
    

    (section 3.3.6 just talks about broadcasts)

    source

    • drwho@beehaw.org ⁨5⁩ ⁨weeks⁩ ago

      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.

      source

      • dan@upvote.au ⁨5⁩ ⁨weeks⁩ ago

        I wasn’t disagreeing with you :) or at least I think I wasn’t. I was just quoting the RFC you linked to.

        source
• AndrasKrigare@beehaw.org ⁨5⁩ ⁨weeks⁩ ago

  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.

  source
• TehPers@beehaw.org ⁨1⁩ ⁨month⁩ ago

  While I agree, it makes connecting to localhost as easy as http://0:8080/ (for port 8080, but omit for port 80)

  source

  • dan@upvote.au ⁨1⁩ ⁨month⁩ ago

    it makes connecting to localhost as easy as http://0:8080/ (for port 8080, but omit for port 80).

    The thing is that it’s not supposed to work, so it’s essentially relying N undefined behaviour. Typing [::1]:8080 is nearly as easy.

    skimming through these PRs, at least for WebKit, I don’t see tests for shorthand IPs like 0 (and no Apple device to test with). What are the chances they missed those…?

    I haven’t seen the PRs, but IP comparison should really be using the binary form of the IPv4 address (a 32-bit number), not the human-friendly form.

    source