Unified Computing SystemHardware / appliance · Cisco
CVE-2012-4087
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 · uneditedA cluster setup script for fabric interconnect devices in Cisco Unified Computing System (UCS) allows remote attackers to execute arbitrary commands via invalid parameters, aka Bug ID CSCtg20793.
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 confidenceThis is a command injection vulnerability in Cisco Unified Computing System (UCS) fabric interconnect devices. The cluster setup script fails to properly validate input parameters, allowing remote attackers to inject and execute arbitrary commands on affected devices.
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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco UCS fabric interconnect hardwareReview system inventory or physically inspect device labels to confirm the hardware is a Cisco UCS fabric interconnect model. Check the system management interface for Cisco UCS Manager identification.Affected if The device is a Cisco Unified Computing System fabric interconnect running any firmware version.
-
Verify cluster setup script accessibilityCheck if the cluster setup interface or service is exposed on the management network. Review access control lists or firewall rules governing access to the UCS Manager setup ports (typically TCP/443 for HTTPS management).Affected if The cluster setup interface is accessible from untrusted networks without proper network segmentation.
-
Review management interface exposureAudit network accessibility of UCS Manager management interfaces (IPMI, SSH, HTTPS). Determine if interfaces are directly exposed to the internet or untrusted VLANs.Affected if Management interfaces are reachable from networks outside the trusted administrative zone.
-
Inspect for suspicious processes or command executionIf shell access is available, review running processes and recent command history on the fabric interconnect for unexpected or unauthorized commands that may indicate exploitation.Affected if Unexpected commands or processes are found in system logs or command history.
A user is affected if they operate any version of Cisco UCS fabric interconnect hardware with exposed management or cluster setup interfaces accessible from untrusted networks.
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 relevant Cisco UCS firmware patches or updates that address Bug ID CSCtg20793. Restrict network access to management interfaces and monitor for unauthorized access attempts.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4087 — 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-4087 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