# CVE-2016-6838: Weak cryptography in n/a

> Remote attackers can decrypt sensitive data by exploiting insecure SSH encryption algorithms in Huawei server firmware.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-389p-6whp-pg38

## What is CVE-2016-6838?

CVE-2016-6838 is a high-severity vulnerability in n/a, published on 7 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei X6800 and XH620 V3 servers with software before V100R003C00SPC606, RH1288 V3 servers with software before V100R003C00SPC613, RH2288 V3 servers with software before V100R003C00SPC617, CH140 V3 and CH226 V3 servers with software before V100R001C00SPC122, CH220 V3 servers with software before V100R001C00SPC201, and CH121 V3 and CH222 V3 servers with software before V100R001C00SPC202 might allow remote attackers to decrypt encrypted data and consequently obtain sensitive information by leveraging selection of an insecure SSH encryption algorithm.

Weakness: CWE-310, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 9 products.


Products: Huawei Ch121 V3 Server Firmware, Huawei Ch140 V3 Server Firmware, Huawei Ch220 V3 Server Firmware, Huawei Ch222 V3 Server Firmware, Huawei Ch226 V3 Server Firmware, Huawei Rh1288 V3 Server Firmware, Huawei Rh2288 V3 Server Firmware, Huawei X6800 V3 Server Firmware, Huawei Xh620 V3 Server Firmware.

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

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

## Is CVE-2016-6838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6838 is a high-severity vulnerability in n/a, published on 7 Sep 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-6838 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-6838/ (Markdown: https://insights.sbomify.com/CVE-2016-6838/index.md)
```

## Sources

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

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