|Home > Security Bulletins > S2-014|
A vulnerability introduced by forcing parameter inclusion in the URL and Anchor Tag allows remote command execution, session access and manipulation and XSS attacks
Who should read this
All Struts 2 developers and users
Impact of vulnerability
Remote command execution, remote server context manipulation, injection of malicious client side code
Maximum security rating
Developers should immediately upgrade to Struts 126.96.36.199
Struts 2.0.0 - Struts 188.8.131.52
Eric Kobrin and Douglas Rodrigues (Akamai), Coverity Security Research Laboratory, NSFOCUS Security Team
The main scope of that attribute is to understand whether includes http request parameter or not.
The allowed values of includeParams are:
A request that included a specially crafted request parameter could be used to inject arbitrary OGNL code into the stack, afterward used as request parameter of an URL or A tag , which will cause a further evaluation.
The second evaluation happens when the URL/A tag tries to resolve every parameters present in the original request.
This lets malicious users put arbitrary OGNL statements into any request parameter (not necessarily managed by the code) and have it evaluated as an OGNL expression to enable method execution and execute arbitrary methods, bypassing Struts and OGNL library protections.
The issue was originally addressed by Struts 184.108.40.206 and Security Announcement S2-013. However, the solution introduced with 220.127.116.11 did not address all possible attack vectors, such that every version of Struts 2 before 18.104.22.168 is still vulnerable to such attacks.
As you will notice, in this case, there is no way to escape/sanitize the malicious parameter, since it's not an expected parameter and even will not get evaluated the request parameters are processed.
The URL rendering subsystem was changed to not pass any parameter name or value to OGNL evaluation.
The MemberAccess component's allowStaticMethodAccess property is now immutable.