Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include 0.0.0.0 in the same group à 127.0.0.0/8 #24

Closed
randomstuff opened this issue Oct 22, 2020 · 5 comments
Closed

Include 0.0.0.0 in the same group à 127.0.0.0/8 #24

randomstuff opened this issue Oct 22, 2020 · 5 comments

Comments

@randomstuff
Copy link

randomstuff commented Oct 22, 2020

On Linux and MacOS, trying to connect to 0.0.0.0 actually connects to the local machine. This can be used for DNS rebinding attacks. As a consequence 0.0.0.0 should be included in the same group à 127.0.0.0/8 (i.e. private or local).

@annevk
Copy link

annevk commented Oct 23, 2020

Per https://en.wikipedia.org/wiki/0.0.0.0 it seems we could also attempt to define that in the context of browsers this results in a network error.

@mikewest
Copy link
Member

this results in a network error.

That seems like a very reasonable outcome to me.

@letitz
Copy link
Collaborator

letitz commented Nov 10, 2020

Where would be the right place to specify that behavior across browsers? I'm not sure this spec is a natural fit.

@annevk
Copy link

annevk commented Nov 10, 2020

I've been thinking Fetch, also for https://tools.ietf.org/html/draft-west-let-localhost-be-localhost. (It'll need to say things about DNS anyway for state partitioning efforts.)

@letitz
Copy link
Collaborator

letitz commented Nov 23, 2020

Per #30, we will consider 0.0.0.0/8 to be private. It would also be good to standardize the error in Fetch, though that is not needed to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants