CVE-2014-0966
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 · uneditedSQL injection 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 execute arbitrary SQL commands 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 confidenceSQL injection vulnerability in the GDS (Generic Data Services) component of IBM InfoSphere Master Data Management allows remote authenticated users to execute arbitrary SQL commands. The vulnerability affects Collaborative Edition versions 10.x and 11.x before 11.0-FP5, and Server for Product Information Management versions 9.x through 11.x before 11.3-IF2.
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= 10.0= 10.1= 11.0= 11.3= 9.0= 9.1= 10.0= 10.0.0.1= 10.0.1= 10.1= 10.1.0.1= 10.1.0.2= 11.0= 11.3CVSS 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
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM InfoSphere Master Data Management versionLocate and inspect the version information through IBM Installation Manager, version.info file in the installation directory, or by querying the product through its administrative interface.Affected if Version is 10.0, 10.1, 11.0, or 11.3 for Collaborative Edition; or 9.0, 9.1, 10.0, 10.0.0.1, 10.0.1, 10.1, 10.1.0.1, 10.1.0.2, 11.0, or 11.3 for Server for Product Information Management
-
Confirm the product edition typeDetermine whether the installation is Collaborative Edition or Server for Product Information Management, as each has different affected version ranges and patch levels.Affected if Running Collaborative Edition versions 10.x or 11.x before 11.0-FP5, or Server for Product Information Management versions 9.x through 11.x before 11.3-IF2
-
Verify if GDS (Generic Data Services) component is configuredInspect the IBM InfoSphere MDM configuration files and administrative console to determine whether the GDS component is enabled. Check for GDS-related configuration in the component settings.Affected if GDS component is present and active in the environment
The environment is affected if the installed version matches one of the listed affected versions AND the GDS component is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply IBM Fix Pack 11.0-FP5 for Collaborative Edition or Interim Fix 11.3-IF2 for Product Information Management. As a compensating control, restrict database access permissions for the application service account to principle of least privilege until the patch can be applied.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0966 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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