News for hackers. Stuff that matters.
Re:Feedback wanted: CORS for private networks (RFC1918) by janci on Tuesday November 10, 2020 @06:33PM (#25053565)
I don't get it. What's wrong with normal CORS? They do work for private networks. Also I don't think browsers are the right place to do this kind of protection.
Re:Feedback wanted: CORS for private networks (RFC1918) by cratermoon on Tuesday November 10, 2020 @08:14PM (#25054417)
It says right there in the proposal

> status quo CORS protections don’t protect against the kinds of attacks discussed here as they rely only on CORS-safelisted methods and CORS-safelisted request-headers. No preflight is triggered, and the attacker doesn’t actually care about reading the response, as the request itself is the CSRF attack.

Re:Feedback wanted: CORS for private networks (RFC1918) by janci on Wednesday November 11, 2020 @01:56AM (#25056118)
Ok, this will protect old unpatched vulnerable devices. But what will prevent a negligent manufacturer that uses HTTP GET without CSFR protection to apply configuration to the device from just adding the CORS opt-in header everywhere? I mean it would be the simplest solution for them.
Re:Feedback wanted: CORS for private networks (RFC1918) by zeroimpl on Tuesday November 10, 2020 @10:44PM (#25055297)
But what about those vulnerabilities is specific to being on a private network? If we can find a public website with the same vulnerability, will we start enforcing stricter CORS requirements everywhere?