# CVE-2016-8754: Hardcoded credentials in OceanStor 5600 V3 V300R003C00

> Attackers can use hardcoded SSH keys to authenticate and log in to Huawei OceanStor storage devices, gaining unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-43cg-qpw3-5c5w

## What is CVE-2016-8754?

CVE-2016-8754 is a high-severity vulnerability in OceanStor 5600 V3 V300R003C00, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei OceanStor 5600 V3 V300R003C00 has a hardcoded SSH key vulnerability; the hardcoded keys are used to encrypt communication data and authenticate different nodes of the devices. An attacker may obtain the hardcoded keys and log in to such a device through SSH.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Huawei Oceanstor 5600 V3 Firmware.

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

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

## Is CVE-2016-8754 being exploited?

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

## Other vulnerabilities in OceanStor 5600 V3 V300R003C00

- [CVE-2016-8801](https://insights.sbomify.com/CVE-2016-8801/): Command injection in OceanStor 5600 V3 V300R003C00C10 and earlier versions (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8754 is a high-severity vulnerability in OceanStor 5600 V3 V300R003C00, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8754 in the wild and no public exploit code.

Affected product: OceanStor 5600 V3 V300R003C00. 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-8754/ (Markdown: https://insights.sbomify.com/CVE-2016-8754/index.md)
```

## Sources

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

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