Re:Security patch releases to Rails 2.3.x, 3.0.x
by nbpoole on Tuesday February 08, 2011 @10:42PM
(#2196181)
To be perfectly clear, Sam is not wrong. Flash and Java both let you issue requests with that header. However, if you try and make a cross-origin request, they'll both throw exceptions unless you have permission (in the form of a crossdomain.xml file). I assume that's where the redirects come into play, although I can't imagine how you redirect someone's POST request to a different domain.
[ Parent
| on HN ]
Re:Security patch releases to Rails 2.3.x, 3.0.x
by tptacek on Tuesday February 08, 2011 @10:45PM
(#2196186)
I'm just messing with you both.
Resetting sessions on CSRF failures is going to suck for us.
Re:Security patch releases to Rails 2.3.x, 3.0.x
by bonzoesc on Tuesday February 08, 2011 @11:59PM
(#2196419)
Is there any reason to reset the session on a CSRF failure vs. just failing the request? Seems like you could have fun DOSing people from their sessions on other sites with that default behavior.
Re:Security patch releases to Rails 2.3.x, 3.0.x
by nbpoole on Wednesday February 09, 2011 @12:28AM
(#2196492)
That's right. Of course, without knowing more details about the vulnerability, it's hard to say whether there's a benefit to ending the session.
Re:Security patch releases to Rails 2.3.x, 3.0.x
by emerose on Wednesday February 09, 2011 @02:16AM
(#2196723)
I don't have any inside information on this, but my guess is that this is going to come down to confusion about 302/303/307 redirects. In theory, clients receiving a 302 in response to a POST are supposed to re-send the POST wherever the redirect leads; in practice, clients do all kinds of different things. This feels like just the kind of weird edge case that defeats fragile security mechanisms like crossdomain.xml.