# CVE-2022-50800: H3C SSL VPN n/a Username Enumeration via Login Script Credential Verification

> Attackers can enumerate valid usernames via the login script, exposing user account existence information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-m8f6-rrcx-mrm3

## What is CVE-2022-50800?

CVE-2022-50800 is a medium-severity vulnerability in Hangzhou H3C Technologies H3C SSL VPN, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

H3C SSL VPN contains a user enumeration vulnerability that allows attackers to identify valid usernames through the 'txtUsrName' POST parameter. Attackers can submit different usernames to the login_submit.cgi endpoint and analyze response messages to distinguish between existing and non-existing accounts.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2022-50800?


## How do I fix CVE-2022-50800?

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

## Is CVE-2022-50800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50800 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50800 and fix it if it is affected.

What it is: CVE-2022-50800 is a medium-severity vulnerability in Hangzhou H3C Technologies H3C SSL VPN, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50800 exists.

Affected product: Hangzhou H3C Technologies H3C SSL VPN. 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-2022-50800/ (Markdown: https://insights.sbomify.com/CVE-2022-50800/index.md)
```

## Sources

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

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