CVE-2016-9714

8.8 HIGH

📋 TL;DR

This CSRF vulnerability in IBM InfoSphere Master Data Management Server allows attackers to trick authenticated users into performing unauthorized actions on their behalf. Affected users are those running vulnerable versions of IBM InfoSphere MDM Server who access the application through a web browser.

💻 Affected Systems

Products:
  • IBM InfoSphere Master Data Management Server
Versions: 10.1, 11.0, 11.3, 11.4, 11.5, 11.6
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using web interface are affected; requires user authentication to exploit.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of MDM data integrity through unauthorized data modifications, privilege escalation, or data exfiltration by tricking administrators into performing malicious actions.

🟠

Likely Case

Unauthorized data manipulation or configuration changes by tricking authenticated users into submitting forged requests.

🟢

If Mitigated

Limited impact with proper CSRF protections, same-origin policies, and user awareness training in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated user interaction; CSRF attacks are well-understood and tools exist to generate payloads.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply fixes per IBM Security Bulletin

Vendor Advisory: http://www.ibm.com/support/docview.wss?uid=swg22006608

Restart Required: Yes

Instructions:

1. Review IBM Security Bulletin for specific fix versions. 2. Apply IBM-provided patches. 3. Restart affected services. 4. Verify CSRF protections are enabled.

🔧 Temporary Workarounds

Implement CSRF Tokens

all

Add anti-CSRF tokens to all state-changing requests

SameSite Cookie Attribute

all

Set SameSite=Strict or SameSite=Lax on session cookies

🧯 If You Can't Patch

  • Implement web application firewall with CSRF protection rules
  • Require re-authentication for sensitive operations and use multi-step confirmation for state-changing actions

🔍 How to Verify

Check if Vulnerable:

Check if CSRF tokens are missing from forms and state-changing requests in web interface

Check Version:

Check IBM InfoSphere MDM version through admin console or configuration files

Verify Fix Applied:

Verify CSRF tokens are present and validated in all POST/PUT/DELETE requests

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed state-changing requests from same user
  • Unusual request patterns without referrer headers

Network Indicators:

  • Cross-origin requests to state-changing endpoints
  • Requests missing CSRF tokens

SIEM Query:

source="web_server" AND (method="POST" OR method="PUT" OR method="DELETE") AND csrf_token="missing"

🔗 References

📤 Share & Export