Unified Computing SystemHardware / appliance · Cisco
CVE-2012-4117
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 fabric-interconnect component in Cisco Unified Computing System (UCS) does not properly verify X.509 certificates, which allows man-in-the-middle attackers to watch SSL KVM video-channel traffic or modify this traffic via a crafted certificate, aka Bug ID CSCtr73033.
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 confidenceThe fabric-interconnect component in Cisco Unified Computing System (UCS) fails to properly validate X.509 certificates during SSL connections for the KVM (Keyboard-Video-Mouse) video channel. This certificate validation flaw allows man-in-the-middle attackers to intercept, view, and potentially modify KVM traffic by presenting a crafted certificate.
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
all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco UCS fabric-interconnect is in useIdentify if the environment contains Cisco Unified Computing System with fabric-interconnect components. Check system inventory or running configuration for 'fabric-interconnect' modules.Affected if System does not have Cisco UCS fabric-interconnect components
-
Check if KVM over IPMI/SSL is enabledReview the fabric-interconnect KVM settings. Look for KVM or IPMI over SSL configuration using 'show kvm session' or similar management interface commands.Affected if KVM over SSL/IPMI is not enabled - the vulnerability requires this feature to be active
-
Verify patch CSCtr73033 statusCheck the current software/firmware version and patch status on the fabric-interconnect. Look for mention of CSCtr73033 in the installed patches or firmware release notes.Affected if Patch CSCtr73033 is not applied and KVM over SSL is active - the certificate validation flaw exists in unpatched versions
A user is affected if they have Cisco UCS fabric-interconnect with KVM over SSL enabled and the CSCtr73033 patch has not been applied to enforce proper X.509 certificate validation.
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 the Cisco patch for Bug ID CSCtr73033 to the UCS fabric-interconnect component to enforce proper X.509 certificate validation on SSL KVM connections.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4117 — 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-2012-4117 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