# CVE-2016-1313: Hardcoded credentials in n/a

> Remote attackers can gain root access to Cisco UCS Invicta appliances due to improperly stored default SSH private keys.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gccx-g2pg-5r7x

## What is CVE-2016-1313?

CVE-2016-1313 is a critical vulnerability in n/a, published on 6 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2016-1313?

It affects 1 product.


Products: Cisco Ucs Invicta C3124sa Appliance.

## How do I fix CVE-2016-1313?

No fix has been published for CVE-2016-1313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-1313 being exploited?

There is no known exploitation of CVE-2016-1313 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-1404](https://insights.sbomify.com/CVE-2016-1404/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1313 and fix it if it is affected.

What it is: CVE-2016-1313 is a critical vulnerability in n/a, published on 6 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1313 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1313/ (Markdown: https://insights.sbomify.com/CVE-2016-1313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1313
- OSV: https://osv.dev/vulnerability/CVE-2016-1313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1313/
Summaries are generated and may contain mistakes; the official description above is the record.