Unified Computing SystemHardware / appliance · Cisco

CVE-2012-4115

MEDIUM · 5.8 CVSS v2.0 Published 2013-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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) does not encrypt KVM virtual-media data, which allows man-in-the-middle attackers to obtain sensitive information by sniffing the network or modify this traffic by inserting packets into the client-server data stream, aka Bug ID CSCtr72964.

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

The Cisco UCS fabric-interconnect component fails to encrypt KVM (Keyboard-Video-Mouse) virtual-media traffic, transmitting data in cleartext. This allows man-in-the-middle attackers on the network path to passively sniff sensitive information from KVM sessions or actively inject/modify packets to manipulate the client-server communication stream.

MitigationApply the Cisco patch for bug ID CSCtr72964 to enable encryption for KVM virtual-media traffic in the UCS fabric-interconnect. Until patched, restrict network access to the management interface using VLAN segmentation or ACLs to reduce MITM exposure.

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 SystemHardware / appliance
Affected:all versions

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

AV:N/AC:M/Au:N/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco UCS fabric-interconnect in use
    Identify if the system is a Cisco UCS environment by logging into UCS Manager and checking the system inventory or chassis overview for fabric-interconnect components
    Affected if The system is a Cisco UCS fabric-interconnect and all versions are affected until the patch is applied
  2. Locate KVM virtual-media configuration
    In UCS Manager, navigate to the KVM virtual-media settings under the fabric-interconnect or server management section where KVM configuration is stored
    Affected if KVM virtual-media is enabled and accessible through the UCS Manager interface
  3. Check KVM encryption status
    Examine the KVM virtual-media configuration settings for an encryption or security option; verify whether encryption is enabled for the KVM session traffic
    Affected if KVM virtual-media is present but encryption is disabled or not explicitly enabled in the configuration
  4. Verify patch CSCtr72964 application
    Check the UCS Manager version or firmware version associated with the fabric-interconnect; compare against the version that includes the CSCtr72964 fix or check the patch status in the system
    Affected if The fabric-interconnect firmware or UCS Manager version does not include the CSCtr72964 patch that enables KVM encryption

A user is affected if they are running any version of Cisco UCS fabric-interconnect with KVM virtual-media enabled and the CSCtr72964 patch has not been applied to enable encryption for KVM traffic.

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 Cisco patch for bug ID CSCtr72964 to enable encryption for KVM virtual-media traffic in the UCS fabric-interconnect. Until patched, restrict network access to the management interface using VLAN segmentation or ACLs to reduce MITM exposure.

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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