In csrf-magic before 1.0.4, if $GLOBALS['csrf']['secret'] is not configured, the Anti-CSRF Token used is predictable and would permit an attacker to bypass the CSRF protections, because an automatically generated secret is not used.
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Link | Tags |
---|---|
http://repo.or.cz/csrf-magic.git/commit/9d2537f70d58b16aeba89779aaf1573b8d618e11 | third party advisory patch |
http://repo.or.cz/csrf-magic.git/blob/HEAD:/NEWS.txt | third party advisory release notes |
http://csrf.htmlpurifier.org/news/2013/0717-1.0.4-released | release notes vendor advisory |