35
edits
Security/CSP/CSRFModule: Difference between revisions
Jump to navigation
Jump to search
→Open Issues
| Line 63: | Line 63: | ||
This section contains a list of open issues. | This section contains a list of open issues. | ||
*Any policy governing the sending of cookies to URIs other than <tt>self</tt> requires enforcement of the policy over all HTTP redirects encountered while loading the URI. (Presumably <tt>self</tt> is in control of its redirects.) CSP | *Any policy governing the sending of cookies to URIs other than <tt>self</tt> requires enforcement of the policy over all HTTP redirects encountered while loading the URI. (Presumably <tt>self</tt> is in control of its redirects.) Enforcement of CSP policies over redirects may be in conflict with [[Security/CSP/BaseModule|BaseModule]], if BaseModule defines CSP policies to be non-composeable, and any redirect or the resource declares a CSP policy. | ||
*The attacker could bypass the defense by hyperlinking to attacker.com, which isn't using CSP, and then submit the CSRF request from there. | *The attacker could bypass the defense by hyperlinking to attacker.com, which isn't using CSP, and then submit the CSRF request from there. | ||
**To address this threat, form submission should only be allowed to <tt>self</tt> URIs when <tt>anti-csrf</tt> is enabled (the allowed set of URIs should be made extensible by other policy declarations). | **To address this threat, form submission should only be allowed to <tt>self</tt> URIs when <tt>anti-csrf</tt> is enabled (the allowed set of URIs should be made extensible by other policy declarations). | ||