CVE Vulnerabilities

CVE-2014-0969

Cross-Site Request Forgery (CSRF)

Published: Aug 17, 2014 | Modified: Aug 29, 2017
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Cross-site request forgery (CSRF) vulnerability in the GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.x and 11.x before 11.0-FP5 and InfoSphere Master Data Management Server for Product Information Management 9.x through 11.x before 11.3-IF2 allows remote authenticated users to hijack the authentication of arbitrary users.

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
Infosphere_master_data_management_server_for_product_information_management Ibm 10.0.0.1 10.0.0.1
Infosphere_master_data_management Ibm 10.1 10.1
Infosphere_master_data_management_server_for_product_information_management Ibm 9.1 9.1
Infosphere_master_data_management Ibm 10.0 10.0
Infosphere_master_data_management_server_for_product_information_management Ibm 10.0 10.0
Infosphere_master_data_management_server_for_product_information_management Ibm 11.3 11.3
Infosphere_master_data_management_server_for_product_information_management Ibm 10.0.1 10.0.1
Infosphere_master_data_management_server_for_product_information_management Ibm 10.1 10.1
Infosphere_master_data_management Ibm 11.0 11.0
Infosphere_master_data_management_server_for_product_information_management Ibm 10.1.0.1 10.1.0.1
Infosphere_master_data_management_server_for_product_information_management Ibm 11.0 11.0
Infosphere_master_data_management_server_for_product_information_management Ibm 10.1.0.2 10.1.0.2
Infosphere_master_data_management Ibm 11.3 11.3
Infosphere_master_data_management_server_for_product_information_management Ibm 9.0 9.0

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