Multiple cross-site request forgery (CSRF) vulnerabilities in the Web Gateway component in IBM WebSphere MQ File Transfer Edition 7.0.4 and earlier, and WebSphere MQ - Managed File Transfer 7.5, allow remote attackers to hijack the authentication of arbitrary users for requests that (1) add user accounts via the /wmqfteconsole/Filespaces URI, (2) modify permissions via the /wmqfteconsole/FileSpacePermisssions URI, or (3) add MQ Message Descriptor (MQMD) user accounts via the /wmqfteconsole/UploadUsers URI.
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 |
| Websphere_mq |
Ibm |
* |
7.0.4 (including) |
| Websphere_mq |
Ibm |
7.0 (including) |
7.0 (including) |
| Websphere_mq |
Ibm |
7.0.0.1 (including) |
7.0.0.1 (including) |
| Websphere_mq |
Ibm |
7.0.1.0 (including) |
7.0.1.0 (including) |
| Websphere_mq |
Ibm |
7.0.2.0 (including) |
7.0.2.0 (including) |
| Websphere_mq |
Ibm |
7.0.2.2 (including) |
7.0.2.2 (including) |
| Websphere_mq |
Ibm |
7.0.4.0 (including) |
7.0.4.0 (including) |
| Websphere_mq_managed_file_transfer |
Ibm |
7.5 (including) |
7.5 (including) |
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