CVE-2014-3064
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 · uneditedThe GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.x and 11.x before 11.0 FP4 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 allows remote authenticated users to read arbitrary files via a crafted UNIX file parameter.
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 confidenceArbitrary file read vulnerability in the GDS component of IBM InfoSphere Master Data Management allows authenticated remote attackers to read any file on the server filesystem by manipulating a UNIX file parameter, likely through path traversal sequences.
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= 9.0= 9.1CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:M/Au:S/C:C/I:N/A:N
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 IBM InfoSphere MDM installationLocate the IBM InfoSphere Master Data Management installation directory and identify the installed product (Collaboration Server or Server for Product Information Management)Affected if The product is IBM InfoSphere MDM Collaboration Server or Server for Product Information Management
-
Determine installed versionCheck the installed version of IBM InfoSphere MDM against the affected versions: Collaboration Server 10.0, 10.1, or 11.0; or Server for Product Information Management 9.0 or 9.1Affected if The installed version matches exactly 10.0, 10.1, 11.0 (Collaboration Server) or 9.0, 9.1 (PIM Server)
-
Verify GDS component is accessibleDetermine whether the GDS (Green Data Sync or similar data synchronization component) is exposed and accessible on the network or remotelyAffected if The GDS component is network-accessible without proper network restrictions
-
Confirm authentication is in use for GDSReview GDS component configuration to determine if authentication is required or if anonymous/unauthenticated access is possibleAffected if GDS accepts authenticated sessions and the attacker has valid credentials or can obtain them
-
Review for path traversal access attemptsExamine GDS component logs for requests containing traversal sequences such as ../ or absolute paths that attempt to access files outside the intended directoryAffected if Logs show path traversal patterns accessing arbitrary system files
A user is affected if they run an exact version match (10.0, 10.1, 11.0 for Collaboration Server or 9.0, 9.1 for PIM Server) with the GDS component exposed to network access, regardless of authentication status.
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 InfoSphere MDM 11.0 FP4 or later patch; if immediate patching is infeasible, restrict network access to the GDS component to trusted IPs only and monitor for anomalous file access patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3064 — 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-3064 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