CVE-2014-0960
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 · uneditedIBM PureApplication System 1.0 before 1.0.0.4 cfix8 and 1.1 before 1.1.0.4 IF1 allows remote authenticated users to bypass intended access restrictions by establishing an SSH session from a deployed virtual machine.
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 confidenceIBM PureApplication System contains an access control bypass vulnerability where authenticated users can establish SSH sessions from deployed virtual machines, allowing them to circumvent intended security restrictions between the VM and the management infrastructure.
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= 1.0.0.0= 1.0.0.1= 1.0.0.2= 1.0.0.3= 1.0.0.4= 1.1.0.0= 1.1.0.1= 1.1.0.2= 1.1.0.3= 1.1.0.4CVSS 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
- Local
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:S/C:C/I:C/A:C
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 the installed PureApplication System versionAccess the IBM PureApplication System management console or use the system version display command to determine the exact firmware/software versionAffected if The installed version matches any of: 1.0.0.0, 1.0.0.1, 1.0.0.2, 1.0.0.3, 1.0.0.4, 1.1.0.0, 1.1.0.1, 1.1.0.2, 1.1.0.3, or 1.1.0.4
-
Verify if SSH access from deployed VMs is enabledInspect the system security configuration or network access policies within the PureApplication System management interface to determine whether SSH connections originating from virtual machine instances are permittedAffected if SSH access from deployed VMs to the management infrastructure is allowed in the configuration
-
Review access control restrictions between VM and management networkExamine the network segmentation or firewall rules that govern communication between deployed workload instances and the management planeAffected if There are no restrictive controls preventing SSH sessions initiated from deployed VMs, or if existing controls can be bypassed by authenticated users
-
Check for evidence of unauthorized SSH access attemptsReview system authentication and audit logs for SSH connection attempts originating from VM IP ranges to the management network addressesAffected if SSH connections from VM addresses to management infrastructure are logged as successful or attempted
You are affected if your PureApplication System version is 1.0.0.0 through 1.1.0.4 and SSH access from deployed VMs to the management infrastructure is not explicitly blocked by network controls or security policies.
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 Packs 1.0.0.4 cfix8 or 1.1.0.4 IF1 (or later) to address the SSH-based access restriction bypass.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0960 — 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-0960 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