Security Bulletin: IBM Cúram Social Program Management is vulnerable to cross-site request forgery attacks (CVE-2014-6090).

Summary

IBM Cúram Social Program management contains a number of servlets which do not adequately protect against CSRF. This could potentially allow an attacker to affect the integrity of data managed by these servlets.

Vulnerability Details

CVEID: CVE-2014-6090**
DESCRIPTION:** IBM Curam Social Program Management is vulnerable to cross-site request forgery, caused by improper validation of user-supplied input. By persuading an authenticated user to visit a malicious Web site, a remote attacker could send a malformed HTTP. An attacker could exploit this vulnerability to perform cross-site scripting attacks, Web cache poisoning, and other malicious activities.
CVSS Base Score: 3.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/95868 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:S/C:N/I:P/A:N)

Affected Products and Versions

5.2 SP6
6.0 SP2
6.0.3
6.0.4
6.0.5

Remediation/Fixes

_Product _

| _VRMF _| Remediation/First Fix
—|—|—
Cúram SPM| 6.0.5| Visit IBM Fix Central and upgrade to 6.0.5.6 or a subsequent 6.0.5 release.
Cúram SPM| 6.0.4| Visit IBM Fix Central and upgrade to 6.0.4.5 iFix10 or a subsequent 6.0.4 release.
Cúram SPM| 6.0.3| Visit IBM Fix Central and upgrade to 6.0.3.0 iFix8 or a subsequent 6.0.3 release.
Cúram SPM| 6.0 SP2| Visit IBM Fix Central and upgrade to 6.0 SP2 EP26 or a subsequent 6.0 SP2 release.
Cúram SPM| 5.2 SP6| Visit IBM Fix Central and upgrade to 5.2 SP6 EP6 or a subsequent 5.2 SP6 release.

Workarounds and Mitigations

There are a number of options to mitigate this issue. The general premise behind these mitigations is that generally these servlets are more useful in development and test environments than in the live system

Mitigation 1
This issue can be worked around by NOT deploying the following servlets to your live system:
DataMappingEditorCommands
DatastoreEditorCommands
IEGEditorCommands

Mitigation 2
This issue can be worked around by modifying user roles so that these servlets cannot be accessed by any users in the production environment. This can be achieved using standard Curam user interface for security roles.