Cross-site request forgery (CSRF) vulnerability in e107_admin/users_extended.php in e107 before 0.7.26 allows remote attackers to hijack the authentication of administrators for requests that insert cross-site scripting (XSS) sequences via the user_include parameter.
Weakness
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.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| E107 |
E107 |
0.7 |
0.7 |
| E107 |
E107 |
0.7.0 |
0.7.0 |
| E107 |
E107 |
0.7.1 |
0.7.1 |
| E107 |
E107 |
0.7.2 |
0.7.2 |
| E107 |
E107 |
0.7.3 |
0.7.3 |
| E107 |
E107 |
0.7.4 |
0.7.4 |
| E107 |
E107 |
0.7.5 |
0.7.5 |
| E107 |
E107 |
0.7.6 |
0.7.6 |
| E107 |
E107 |
0.7.7 |
0.7.7 |
| E107 |
E107 |
0.7.8 |
0.7.8 |
| E107 |
E107 |
0.7.9 |
0.7.9 |
| E107 |
E107 |
0.7.10 |
0.7.10 |
| E107 |
E107 |
0.7.11 |
0.7.11 |
| E107 |
E107 |
0.7.12 |
0.7.12 |
| E107 |
E107 |
0.7.13 |
0.7.13 |
| E107 |
E107 |
0.7.14 |
0.7.14 |
| E107 |
E107 |
0.7.15 |
0.7.15 |
| E107 |
E107 |
0.7.16 |
0.7.16 |
| E107 |
E107 |
0.7.17 |
0.7.17 |
| E107 |
E107 |
0.7.18 |
0.7.18 |
| E107 |
E107 |
0.7.19 |
0.7.19 |
| E107 |
E107 |
0.7.20 |
0.7.20 |
| E107 |
E107 |
0.7.21 |
0.7.21 |
| E107 |
E107 |
0.7.22 |
0.7.22 |
| E107 |
E107 |
* |
0.7.24 |
Potential Mitigations
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Use the “double-submitted cookie” method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
References