Re: [quicwg/base-drafts] Request forgery attacks (#3995)

[MikkelFJ <[e-mail]>]

Interesting.

In the issue you mention loopback but then goes on to use a local router address.
I was thinking loopback was on the clients machine.

It is often the case that documentation servers run on localhost to display content, and some applications may be written to either directly use a browser interface, or indirectly via electron to a local host.

These types of applications are generally not hardened and therefore comparatively easy to exploit. In the worst case, such application insists on running on port 80 or some other privileged port thereby having elevated permissions.

But, how does this new attack differ from a HTTP redirect from a random web server, where part of the url is designed til trigger a vulnerability?

I can see some level of same domain protection for HTTPS, but as far as I am aware, such protections to not apply to redirects.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3995#issuecomment-672700043