The token check mechanism in Apache Struts 2.0.0 up to and including 2.3.4 does not properly validate the token name configuration parameter, which allows remote malicious users to perform cross-site request forgery (CSRF) attacks by setting the token name configuration parameter to a session attribute.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
apache struts 2.0.11 |
||
apache struts 2.0.9 |
||
apache struts 2.1.3 |
||
apache struts 2.1.2 |
||
apache struts 2.1.8 |
||
apache struts 2.1.8.1 |
||
apache struts 2.0.1 |
||
apache struts 2.0.3 |
||
apache struts 2.0.2 |
||
apache struts 2.3.4 |
||
apache struts 2.1.4 |
||
apache struts 2.2.1 |
||
apache struts 2.1.1 |
||
apache struts 2.1.0 |
||
apache struts 2.0.10 |
||
apache struts 2.0.0 |
||
apache struts 2.3.1.2 |
||
apache struts 2.3.3 |
||
apache struts 2.0.11.2 |
||
apache struts 2.0.11.1 |
||
apache struts 2.0.8 |
||
apache struts 2.0.14 |
||
apache struts 2.0.13 |
||
apache struts 2.2.1.1 |
||
apache struts 2.2.3 |
||
apache struts 2.0.5 |
||
apache struts 2.2.3.1 |
||
apache struts 2.0.6 |
||
apache struts 2.1.5 |
||
apache struts 2.0.12 |
||
apache struts 2.1.6 |
||
apache struts 2.0.4 |
||
apache struts 2.0.7 |
||
apache struts 2.3.1 |
||
apache struts 2.3.1.1 |
Vulmon