dbcve.org
Ucs Invicta C3124sa ApplianceApplication · Cisco

CVE-2016-1313

CRITICAL · 9.8 CVSS v3.0 Published 2016-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Cisco UCS Invicta C3124SA Appliance 4.3.1 through 5.0.1, UCS Invicta Scaling System and Appliance, and Whiptail Racerunner improperly store a default SSH private key, which allows remote attackers to obtain root access via unspecified vectors, aka Bug ID CSCun71294.

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 confidence

The affected Cisco UCS Invicta C3124SA Appliance, UCS Invicta Scaling System/Appliance, and Whiptail Racerunner products ship with a hardcoded/default SSH private key embedded in the firmware. An unauthenticated remote attacker with knowledge of this key can authenticate as root to any affected device over SSH, bypassing all normal authentication controls.

MitigationUpgrade to a patched version as specified in Cisco's advisory. As an interim control, disable direct SSH access from untrusted networks, restrict access via VPN or jump hosts, and implement network segmentation to limit exposure.

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
Ucs Invicta C3124sa ApplianceApplication
Affected:= 4.3.1= 4.5.0= 5.0.1

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product model
    Run 'show version' or 'get system info' on the device CLI to confirm the exact model name (C3124SA, UCS Invicta Scaling System/Appliance, or Whiptail Racerunner)
    Affected if The model is one of Cisco UCS Invicta C3124SA, UCS Invicta Scaling System/Appliance, or Whiptail Racerunner
  2. Check the firmware version
    Run 'show version' or 'get firmware version' to retrieve the installed firmware version
    Affected if The firmware version is 4.3.1, 4.5.0, or 5.0.1 for the C3124SA model, or falls within any affected version range for other listed products
  3. Verify if SSH service is enabled
    Run 'show ssh status' or check the SSH service configuration via the management interface
    Affected if SSH is enabled and accessible from network interfaces
  4. Inspect for hardcoded SSH private keys
    Review SSH configuration files in /etc/ssh/ or the firmware image for any embedded private keys, compare file fingerprints against known defaults
    Affected if A default or hardcoded SSH private key is present in the system configuration or firmware

The system is affected if it is a Cisco UCS Invicta C3124SA, Scaling System/Appliance, or Whiptail Racerunner running an affected firmware version (4.3.1, 4.5.0, 5.0.1 or other vulnerable versions) with SSH enabled and a hardcoded private key present in the firmware.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version as specified in Cisco's advisory. As an interim control, disable direct SSH access from untrusted networks, restrict access via VPN or jump hosts, and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

Contact Cisco for the fixed release - patches for UCS Invicta appliances are released through Cisco's normal support channels

  1. Contact Cisco TAC or visit tools.cisco.com to obtain the security patch for CVE-2016-1313
  2. Request the specific firmware version that addresses the default SSH private key vulnerability (CSCun71294)
  3. Apply the patch following Cisco's standard UCS Invicta update procedures
  4. After patching, verify the SSH service is using unique, newly generated keys rather than any default keys
  5. If no patch is available from Cisco, consider network segmentation to limit exposure to the SSH service
Caveat Review Cisco release notes for any compatibility or configuration changes when upgrading UCS Invicta firmware

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ucs Invicta C3124sa Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1313 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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