The token check mechanism in Apache Struts 2.0.0 through 2.3.4 does not properly validate the token name configuration parameter, which allows remote attackers to perform cross-site request forgery (CSRF) attacks by setting the token name configuration parameter to a session attribute.
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 |
---|---|
https://issues.apache.org/jira/browse/WW-3858 | |
https://exchange.xforce.ibmcloud.com/vulnerabilities/78182 | vdb entry |
http://www.openwall.com/lists/oss-security/2012/09/01/5 | mailing list |
http://secunia.com/advisories/50420 | third party advisory vendor advisory |
http://www.securityfocus.com/bid/55346 | vdb entry |
http://struts.apache.org/2.x/docs/s2-010.html | vendor advisory |
http://www.openwall.com/lists/oss-security/2012/09/01/4 | mailing list |