# CVE-2017-8157: OceanStor 5800 V3 with software V300R002C00 and V300R002C10, OceanStor 6900 V3 V300R001C00 has an information leakage vulnerability.


- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rfhp-6x8p-v5p4

## What is CVE-2017-8157?

CVE-2017-8157 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. OceanStor 5800 V3, OceanStor 6900 V3, published on 22 Nov 2017. 

### Official description

OceanStor 5800 V3 with software V300R002C00 and V300R002C10, OceanStor 6900 V3 V300R001C00 has an information leakage vulnerability. Products use TLS1.0 to encrypt. Attackers can exploit TLS1.0's vulnerabilities to decrypt data to obtain sensitive information.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2017-8157?

It affects 2 products.


Products: Huawei Oceanstor 5800 V3 Firmware, Huawei Oceanstor 6900 V3 Firmware.

## How do I fix CVE-2017-8157?

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

## Is CVE-2017-8157 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. OceanStor 5800 V3, OceanStor 6900 V3

- [CVE-2016-6177](https://insights.sbomify.com/CVE-2016-6177/): Integer overflow in OceanStor 5800 V3 V300R003C00 (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8157 and fix it if it is affected.

What it is: CVE-2017-8157 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. OceanStor 5800 V3, OceanStor 6900 V3, published on 22 Nov 2017. 
Exploitation: There is no known exploitation of CVE-2017-8157 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. OceanStor 5800 V3, OceanStor 6900 V3. 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-2017-8157/ (Markdown: https://insights.sbomify.com/CVE-2017-8157/index.md)
```

## Sources

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

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