Unified Computing SystemHardware / appliance · Cisco
CVE-2012-1313
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 remote debug shell on the PALO adapter card in Cisco Unified Computing System (UCS) allows local users to gain privileges via malformed show-macstats parameters, aka Bug ID CSCub13772.
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 confidenceA privilege escalation vulnerability exists in the remote debug shell of the PALO adapter card in Cisco UCS. Local users can exploit malformed show-macstats parameters to gain elevated privileges, bypassing normal access controls.
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
- Multiple
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:M/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 PALO adapter card presenceIn Cisco UCS Manager, navigate to Equipment > Adaptors or use 'show adaptors' CLI command to list all adapter cards. Look for PALO adapter cards in the inventory.Affected if A PALO adapter card is present in the Cisco UCS environment
-
Verify remote debug shell accessibilityCheck if the remote debug shell feature is enabled on the PALO adapter. This may be accessible via the adapter's service profile or debug interfaces. Use 'show debug-shell status' or similar diagnostic commands if available.Affected if Remote debug shell is enabled or accessible on the PALO adapter
-
Confirm user access to debug shellReview user accounts and privileges associated with the PALO adapter. Check if local users have access to debug shell functionality. Use UCS Manager to audit user roles and debug access permissions.Affected if Local users have debug shell access privileges
-
Check for show-macstats command availabilityIf debug shell is accessible, verify whether the show-macstats command or similar MAC statistics utilities are exposed through the debug interface.Affected if Debug shell provides access to show-macstats or equivalent diagnostic commands
A Cisco UCS environment with a PALO adapter card that has its remote debug shell enabled and accessible to local users 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 firmware patch for Bug ID CSCub13772 to the affected PALO adapter cards. If a patch is unavailable, restrict physical and logical access to the debug shell functionality.
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-1313 — 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-1313 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