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 can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Struts | Apache | 2.3.1.1 | 2.3.1.1 |
Struts | Apache | 2.0.9 | 2.0.9 |
Struts | Apache | 2.0.12 | 2.0.12 |
Struts | Apache | 2.2.3.1 | 2.2.3.1 |
Struts | Apache | 2.1.0 | 2.1.0 |
Struts | Apache | 2.0.0 | 2.0.0 |
Struts | Apache | 2.0.8 | 2.0.8 |
Struts | Apache | 2.0.7 | 2.0.7 |
Struts | Apache | 2.0.4 | 2.0.4 |
Struts | Apache | 2.2.1 | 2.2.1 |
Struts | Apache | 2.1.8.1 | 2.1.8.1 |
Struts | Apache | 2.3.3 | 2.3.3 |
Struts | Apache | 2.3.4 | 2.3.4 |
Struts | Apache | 2.1.3 | 2.1.3 |
Struts | Apache | 2.1.2 | 2.1.2 |
Struts | Apache | 2.1.5 | 2.1.5 |
Struts | Apache | 2.0.1 | 2.0.1 |
Struts | Apache | 2.0.2 | 2.0.2 |
Struts | Apache | 2.1.8 | 2.1.8 |
Struts | Apache | 2.0.11.1 | 2.0.11.1 |
Struts | Apache | 2.0.3 | 2.0.3 |
Struts | Apache | 2.0.14 | 2.0.14 |
Struts | Apache | 2.3.1 | 2.3.1 |
Struts | Apache | 2.0.11 | 2.0.11 |
Struts | Apache | 2.1.6 | 2.1.6 |
Struts | Apache | 2.0.5 | 2.0.5 |
Struts | Apache | 2.2.3 | 2.2.3 |
Struts | Apache | 2.1.4 | 2.1.4 |
Struts | Apache | 2.2.1.1 | 2.2.1.1 |
Struts | Apache | 2.0.11.2 | 2.0.11.2 |
Struts | Apache | 2.0.13 | 2.0.13 |
Struts | Apache | 2.3.1.2 | 2.3.1.2 |
Struts | Apache | 2.1.1 | 2.1.1 |
Struts | Apache | 2.0.6 | 2.0.6 |
Struts | Apache | 2.0.10 | 2.0.10 |