dbcve.org
Infosphere Master Data Management Collaboration ServerApplication · Ibm

CVE-2013-0477

MEDIUM · 6.0 CVSS v2.0 Published 2013-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable 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 scripting (XSS) vulnerabilities in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 and 10.1 before FP1 and InfoSphere Master Data Management Server for Product Information Management 6.0, 9.0, and 9.1 allow remote authenticated users to inject content, and conduct phishing attacks, via unspecified vectors.

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 · moderate confidence

Multiple cross-site scripting (XSS) vulnerabilities in IBM InfoSphere Master Data Management Collaborative Edition 10.0-10.1 before FP1 and MDM Server for PIM versions 6.0, 9.0, and 9.1 allow authenticated users to inject malicious scripts via unspecified input vectors, enabling phishing and content injection attacks.

MitigationApply IBM Fix Pack 1 (FP1) for affected versions or subsequent vendor patches; implement output encoding and input validation for all user-supplied data in web interfaces.

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 Collaboration ServerApplication
Affected:= 10.0.0= 10.0.1
Infosphere Master Data Management Server For Product Information ManagementApplication
Affected:= 6.0.0= 9.0.0= 9.1.0

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/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 the installed version of IBM MDM Collaborative Edition or MDM Server for PIM
    Access the product's About page or version information utility. For MDM Collaborative Edition 10.x, this is typically found in the IBM InfoSphere MDM Collaboration Server administration console or via the versionInfo command in the installation directory. For MDM Server for PIM, check the installed packages via IBM Installation Manager or the WebSphere Application Server administrative console where the application is deployed.
    Affected if The installed version matches 10.0.0, 10.0.1, 6.0.0, 9.0.0, or 9.1.0, indicating the system is running a vulnerable release before FP1.
  2. Confirm the web interface is accessible
    Verify that the IBM MDM web application is exposed by attempting to access the HTTP/HTTPS endpoint used for the MDM collaborative or PIM web interface. This is typically hosted on WebSphere Application Server and accessible on configured ports (often 8080, 8443, or custom ports).
    Affected if The web interface is reachable and responds, indicating the attack surface for XSS exists.
  3. Verify multi-user authentication is enabled
    Confirm that the MDM system is configured to allow multiple user accounts and that user login functionality is active. Check the WebSphere Application Server security settings and the MDM user registry configuration to ensure authenticated user sessions can be established.
    Affected if Multiple user accounts exist or user authentication is enabled, which is required for authenticated XSS exploitation.
  4. Review application logs for indicators of XSS attempts
    Examine IBM WebSphere Application Server logs and IBM MDM application logs for any suspicious script injection patterns in request parameters, particularly in fields where user input is processed without proper encoding.
    Affected if Logs contain unrecognized script tags or XSS probe patterns in user-submitted data, which may indicate attempted exploitation.

A system is affected if it runs IBM InfoSphere MDM Collaborative Edition versions 10.0.0 or 10.1, or MDM Server for PIM versions 6.0.0, 9.0.0, or 9.1.0, with the web interface and user authentication enabled.

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 IBM Fix Pack 1 (FP1) for affected versions or subsequent vendor patches; implement output encoding and input validation for all user-supplied data in web interfaces.

Fix this in Infosphere Master Data Management Collaboration Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0477 — 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-2013-0477 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