Unified Computing SystemHardware / appliance · Cisco
CVE-2012-4112
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 Baseboard Management Controller (BMC) in Cisco Unified Computing System (UCS) allows local users to gain privileges and execute arbitrary commands via crafted command parameters within the command-line interface, aka Bug ID CSCtr43330.
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 local privilege escalation vulnerability in the Baseboard Management Controller (BMC) of Cisco Unified Computing System. An authenticated local user can execute arbitrary commands by providing crafted parameters to the BMC command-line interface, allowing them to escalate privileges beyond their assigned permissions.
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 hardware in environmentCheck system inventory, hardware labels, or management interfaces for Cisco Unified Computing System (UCS) equipment. Look for UCS Manager, UCS C-Series, or B-Series servers.Affected if System is identified as Cisco UCS hardware
-
Verify BMC CLI accessibilityAttempt to access the Cisco Integrated Management Controller (CIMC) or IPMI interface via HTTPS (default port 443) or SSH. Check if the BMC CLI responds to authentication requests.Affected if BMC CLI interface is reachable and accepts authentication
-
Confirm local user accounts on BMCLog into the CIMC/IPMI CLI or web interface and list local user accounts. Look for accounts configured in the user management section of the BMC.Affected if Local user accounts exist in the BMC user database
-
Check BMC firmware versionFrom CIMC web interface, navigate to Admin > Firmware Management or use 'show firmware' in CIMC CLI to display current firmware version.Affected if Firmware version is unknown, unpatched, or cannot be verified as updated for CSCtr43330
-
Audit BMC command loggingReview BMC audit logs or command history for unexpected or unauthorized CLI commands that may indicate exploitation attempts.Affected if Suspicious commands appear in logs or user command history shows privilege escalation patterns
If the environment contains Cisco UCS systems with accessible BMC CLI and local user accounts, and the firmware has not been explicitly patched for CSCtr43330, the 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 the relevant Cisco patch or firmware update for CSCtr43330. If a patch is unavailable, restrict physical and CLI access to the BMC, limit administrative accounts, and monitor for suspicious command patterns.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4112 — 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-4112 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