I think what he's saying is if your CSRF protection is based on a nonce, this vulnerability doesn't break it.
No, but that wasn't my point. My point was that this vulnerability can be (and has been) worked around by using nonces in the header. If you can see the response body, that protection becomes worthless as well (and there is no workaround for that).
Do you need to see the response to do bad things?