dbcve.org
Infosphere Master Data Management ServerApplication · Ibm

CVE-2014-0873

MEDIUM · 6.8 CVSS v2.0 Published 2014-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) Data Stewardship, (2) Business Admin, and (3) Product interfaces in IBM InfoSphere Master Data Management (MDM) Server 8.5 before 8.5.0.82, 9.0.1 before 9.0.1.38, 9.0.2 before 9.0.2.35, 10.0 before 10.0.0.0.26, and 10.1 before 10.1.0.0.15 allow remote attackers to hijack the authentication of arbitrary users.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple cross-site request forgery (CSRF) vulnerabilities exist in IBM InfoSphere Master Data Management Server across Data Stewardship, Business Admin, and Product interfaces. The vulnerabilities allow remote attackers to perform actions on behalf of authenticated users by tricking them into visiting malicious pages, due to missing or inadequate anti-CSRF protections in these web interfaces.

MitigationApply the vendor-supplied patches: upgrade to version 8.5.0.82 or later, 9.0.1.38 or later, 9.0.2.35 or later, 10.0.0.0.26 or later, or 10.1.0.0.15 or later. Until patches are applied, consider implementing SameSite cookie attributes and CSRF tokens at the web proxy or application firewall level as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Infosphere Master Data Management ServerApplication
Affected:= 8.5= 9.0.1= 9.0.2= 10.0= 10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM InfoSphere MDM Server version
    Locate and inspect the installed version of IBM InfoSphere Master Data Management Server using the platform's standard version reporting mechanism (typically via installation directory files, About dialog, or administrative console)
    Affected if The installed version matches any of: 8.5, 9.0.1, 9.0.2, 10.0, or 10.1 (without the corresponding vendor patches applied)
  2. Verify Data Stewardship interface exposure
    Determine if the Data Stewardship web interface is accessible and enabled on the MDM Server environment
    Affected if The Data Stewardship interface is exposed without anti-CSRF token protection or SameSite cookie attributes at the application or proxy level
  3. Verify Business Admin interface exposure
    Determine if the Business Administration web interface is accessible and enabled on the MDM Server environment
    Affected if The Business Admin interface is exposed without anti-CSRF token protection or SameSite cookie attributes at the application or proxy level
  4. Verify Product interface exposure
    Determine if the Product web interface is accessible and enabled on the MDM Server environment
    Affected if The Product interface is exposed without anti-CSRF token protection or SameSite cookie attributes at the application or proxy level
  5. Review web proxy or WAF for CSRF compensating controls
    Inspect the web proxy or application firewall configuration for SameSite cookie attributes or CSRF token enforcement as compensating controls
    Affected if No compensating controls are implemented at the proxy or firewall level and the installed version falls within the affected ranges

You are affected if the installed version is 8.5, 9.0.1, 9.0.2, 10.0, or 10.1 without vendor patches and any of the Data Stewardship, Business Admin, or Product web interfaces are accessible to users without anti-CSRF protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches: upgrade to version 8.5.0.82 or later, 9.0.1.38 or later, 9.0.2.35 or later, 10.0.0.0.26 or later, or 10.1.0.0.15 or later. Until patches are applied, consider implementing SameSite cookie attributes and CSRF tokens at the web proxy or application firewall level as a compensating control.

Fix this in Infosphere Master Data Management Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0873 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data