Unified Computing SystemHardware / appliance · Cisco
CVE-2012-4108
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) allows local users to gain privileges and execute arbitrary operating-system commands via crafted parameters to a file-related command, aka Bug ID CSCtq86554.
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 confidenceLocal privilege escalation vulnerability in the fabric-interconnect component of Cisco Unified Computing System (UCS) allows authenticated local users to execute arbitrary operating-system commands via crafted parameters to a file-related command.
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
- Local
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/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 Cisco UCS deploymentLocate UCS Manager or fabric-interconnect management IP addresses in your network inventory or by checking DNS for 'ucs' or 'fabric-interconnect' hostnamesAffected if Your environment contains Cisco UCS Manager or fabric-interconnect systems
-
Confirm fabric-interconnect component is accessibleAttempt to access the fabric-interconnect CLI or management interface via console, SSH, or GUI. Look for prompts containing 'fabric-interconnect' or 'FI' designationsAffected if You can reach a fabric-interconnect management interface
-
Verify local user accounts exist in UCSLog into UCS Manager and navigate to Admin > User Management > Local Users to list locally-configured accounts, or check /etc/passwd if you have shell access to the fabric-interconnectAffected if Local user accounts are configured in UCS with access to fabric-interconnect
-
Check for shell or elevated accessReview user roles assigned to local accounts in UCS Manager (Admin > User Management > Local Users > User > Role). Look for 'admin', 'aaa', or shell-access rolesAffected if Local users have administrative or shell-access roles on the fabric-interconnect
-
Assess physical and console accessAudit physical access controls and console connectivity to fabric-interconnect ports. Document which personnel have direct accessAffected if Multiple users or untrusted personnel have physical or console access to fabric-interconnect
If you have a Cisco UCS environment with fabric-interconnect components and local user accounts with any level of administrative or shell access, your environment is affected by this privilege escalation vulnerability.
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 Cisco patches for Bug ID CSCtq86554 when available; restrict physical and console access to the fabric-interconnect to trusted administrators only; follow least-privilege principles for local user accounts.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4108 — 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-4108 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