Horde Groupware Web mail 5.1.2 has CSRF with requests to change permissions
Weakness
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.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Groupware |
Horde |
5.1.2 (including) |
5.1.2 (including) |
| Horde3 |
Ubuntu |
lucid |
* |
| Horde3 |
Ubuntu |
precise |
* |
| Horde3 |
Ubuntu |
quantal |
* |
| Horde3 |
Ubuntu |
raring |
* |
| Horde3 |
Ubuntu |
saucy |
* |
| Php-horde |
Ubuntu |
artful |
* |
| Php-horde |
Ubuntu |
bionic |
* |
| Php-horde |
Ubuntu |
cosmic |
* |
| Php-horde |
Ubuntu |
disco |
* |
| Php-horde |
Ubuntu |
eoan |
* |
| Php-horde |
Ubuntu |
esm-apps/bionic |
* |
| Php-horde |
Ubuntu |
esm-apps/xenial |
* |
| Php-horde |
Ubuntu |
raring |
* |
| Php-horde |
Ubuntu |
saucy |
* |
| Php-horde |
Ubuntu |
trusty |
* |
| Php-horde |
Ubuntu |
utopic |
* |
| Php-horde |
Ubuntu |
vivid |
* |
| Php-horde |
Ubuntu |
wily |
* |
| Php-horde |
Ubuntu |
xenial |
* |
| Php-horde |
Ubuntu |
yakkety |
* |
| Php-horde |
Ubuntu |
zesty |
* |
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 [REF-1482].
- 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