Unified Computing SystemHardware / appliance · Cisco
CVE-2012-4110
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 · uneditedrun-script in the fabric-interconnect component in Cisco Unified Computing System (UCS) allows local users to gain privileges by embedding commands in an unspecified parameter, aka Bug ID CSCtq86560.
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 run-script function of the fabric-interconnect component in Cisco Unified Computing System (UCS). The vulnerability allows local users to inject and execute commands by embedding them in an unspecified parameter, potentially gaining elevated privileges on the affected system.
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.
-
Confirm Cisco UCS installationIdentify if the system is running Cisco Unified Computing System (UCS) by checking system inventory, hardware documentation, or UCS Manager interfaceAffected if The system is identified as Cisco UCS with fabric-interconnect component
-
Verify fabric-interconnect management accessCheck if the fabric-interconnect management interface is reachable via SSH, UCS Manager, or CLI (connect fabric-interconnect)Affected if Management interface to fabric-interconnect is accessible from the local system
-
Check for local user accountsList local user accounts configured on the fabric-interconnect using 'show local-user' in UCS Manager or via CLIAffected if Local user accounts exist on the fabric-interconnect with any privilege level
-
Verify run-script function availabilityCheck if the run-script or similar scripting functionality is exposed on the fabric-interconnect (consult UCS documentation for available commands)Affected if Run-script or command injection-capable functions are accessible to local users
-
Assess user privilege levelsReview the privilege level of local users who could access the fabric-interconnect management interfacesAffected if Local users with access to fabric-interconnect have privileges that could be escalated
A system is affected if it runs Cisco UCS with fabric-interconnect component and local users have access to management interfaces where the run-script function can be exploited for command injection.
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 appropriate Cisco patch for CSCtq86560 when available, and restrict local user access to the fabric-interconnect management interfaces to minimize attack surface.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4110 — 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-4110 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