# CVE-2022-33735: Auth bypass in WS7200-10

> Attackers on the local network can brute-force passwords to gain unauthorized access and disclose sensitive system information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-rmm9-xcr8-ff62

## What is CVE-2022-33735?

CVE-2022-33735 is a medium-severity authentication bypass vulnerability in WS7200-10, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a password verification vulnerability in WS7200-10 11.0.2.13. Attackers on the LAN may use brute force cracking to obtain passwords, which may cause sensitive system information to be disclosed.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Huawei Ws7200-10 Firmware.

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

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

## Is CVE-2022-33735 being exploited?

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

## Other vulnerabilities in WS7200-10

- [CVE-2021-46835](https://insights.sbomify.com/CVE-2021-46835/): Other in WS7200-10 (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33735 is a medium-severity authentication bypass vulnerability in WS7200-10, published on 20 Sep 2022. 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-2022-33735 in the wild and no public exploit code.

Affected product: WS7200-10. 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-33735/ (Markdown: https://insights.sbomify.com/CVE-2022-33735/index.md)
```

## Sources

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

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