9 ms·
The request has to be issued by the attacker from the victim's browser. If the attacker can do that, why is he unable to read the response to that request? Edi
by z-factor 13y ago
The request has to be issued by the attacker from the victim's browser. If the attacker can do that, why is he unable to read the response to that request?
Edit: I think I can see a scenario where a third-party website does these requests via an <iframe> or an <img>. I'm not sure there's a way to do POST quite as easily.
- tptacek 13y agoDo 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.
- z-factor 13y agoI 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.
- chopin 13y agoWould it be possible to thwart this attack (BREACH) by issuing fresh CSRF tokens for each requests?
- z-factor 13y agoYes.
- homakov 13y agoOracle padding