# CVE-2016-6825: Auth bypass in n/a

> Remote attackers can obtain passwords via brute-force attacks due to missing authentication protection mechanisms on Huawei servers.

- **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:** 7 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9mvx-mp3h-cm56

## What is CVE-2016-6825?

CVE-2016-6825 is a critical authentication bypass 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 XH620 V3, XH622 V3, and XH628 V3 servers with software before V100R003C00SPC610, RH1288 V3 servers with software before V100R003C00SPC613, RH2288 V3 servers with software before V100R003C00SPC617, and RH2288H V3 servers with software before V100R003C00SPC515 allow remote attackers to obtain passwords via a brute-force attack, related to "lack of authentication protection mechanisms."

Weakness: CWE-285 (Improper Authorization)

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

It affects 6 products.


Products: Huawei Rh1288 V3 Server Firmware, Huawei Rh2288 V3 Server Firmware, Huawei Rh2288h V3 Server Firmware, Huawei Xh620 V3 Server Firmware, Huawei Xh622 V3 Server Firmware, Huawei Xh628 V3 Server Firmware.

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

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

## Is CVE-2016-6825 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6899](https://insights.sbomify.com/CVE-2016-6899/): Weak cryptography in n/a (high 7.5)
- [CVE-2016-6900](https://insights.sbomify.com/CVE-2016-6900/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6825 is a critical authentication bypass 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-6825 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-6825/ (Markdown: https://insights.sbomify.com/CVE-2016-6825/index.md)
```

## Sources

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

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