Unified Computing System Infrastructure And Unified Computing System SoftwareOperating system · Cisco

CVE-2012-1339

MEDIUM · 5.0 CVSS v2.0 Published 2012-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The Fabric Interconnect component in Cisco Unified Computing System (UCS) 2.0 allows remote attackers to cause a denial of service (process crash) via an attempted SSH session, aka Bug ID CSCtt94543.

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

The Fabric Interconnect component in Cisco Unified Computing System (UCS) version 2.0 contains a denial-of-service vulnerability where remote attackers can crash a process by initiating an SSH session. The vulnerability is triggered during the SSH authentication attempt, causing the affected process to fail.

MitigationApply the relevant Cisco patch (referenced as CSCtt94543) to upgrade the UCS Fabric Interconnect beyond version 2.0. Until patched, restrict SSH access to the Fabric Interconnect to trusted management networks only.

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
Unified Computing System Infrastructure And Unified Computing System SoftwareOperating system
Affected:= 2.0\(1q\)

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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 Cisco UCS Fabric Interconnect version
    Log into UCS Manager or use CLI command 'show version' on the Fabric Interconnect to display the running software version
    Affected if The version displayed is 2.0(1q) or falls within the 2.0.x release train
  2. Verify SSH service is enabled on Fabric Interconnect
    Check the Fabric Interconnect configuration using 'show running-config | include ssh' or access UCS Manager to verify SSH service status under the Management -> Services section
    Affected if SSH is enabled and running on the Fabric Interconnect (the vulnerability is triggered during SSH authentication attempt)
  3. Determine SSH accessibility from network
    Use 'show ip access-list' or network scanning from external locations to determine if TCP port 22 (SSH) is reachable from management networks or untrusted sources
    Affected if SSH port 22 on the Fabric Interconnect is accessible from networks outside trusted management interfaces
  4. Confirm Fabric Interconnect model and software train
    Use 'show inventory' or UCS Manager to confirm the device is a Fabric Interconnect running Cisco UCS Infrastructure software, not third-party or standalone networking gear
    Affected if The device is a Cisco UCS Fabric Interconnect running the 2.0 infrastructure software train

You are affected if your Fabric Interconnect runs version 2.0(1q) with SSH enabled and accessible from your network, allowing remote attackers to trigger the DoS during SSH authentication.

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 relevant Cisco patch (referenced as CSCtt94543) to upgrade the UCS Fabric Interconnect beyond version 2.0. Until patched, restrict SSH access to the Fabric Interconnect to trusted management networks only.

Fix this in Unified Computing System Infrastructure And Unified Computing System Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1339 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-1339 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