News for hackers. Stuff that matters.
Re:Security advisory: Breach and Django by tptacek on Tuesday August 06, 2013 @11:52AM (#6167273)
Do you understand how CSRF works? Just think of it in terms of CSRF. Since the attacker is trying to infer page content, they don't care that the server rejects all the probing requests, so CSRF protection doesn't help you as the attacker carries out the BREACH/CRIME stuff. If the result of the attack is an inferred CSRF token, they then cap the whole exploit off with a (now working) actual CSRF attack.
Re:Security advisory: Breach and Django by z-factor on Tuesday August 06, 2013 @12:01PM (#6167340)
I understand how the attack works, the question was about how a practical exploit would actually be carried out. I've figured out how one would issue GET requests from the right environment, but I don't know if the same is possible for POST.
Re:Security advisory: Breach and Django by wglb on Tuesday August 06, 2013 @12:15PM (#6167425)
It is just as possible. POST csrf exploits add between two and three minutes to an attacker to craft the request differently.
Re:Security advisory: Breach and Django by tptacek on Tuesday August 06, 2013 @12:38PM (#6167580)
Just in case you weren't clear on this already: CSRF works just fine against POST endpoints. Think Javascript.
Re:Security advisory: Breach and Django by chopin on Wednesday August 07, 2013 @08:16AM (#6172246)
Would it be possible to thwart this attack (BREACH) by issuing fresh CSRF tokens for each requests?
Re:Security advisory: Breach and Django by z-factor on Thursday August 08, 2013 @07:59PM (#6182818)
Yes.