# CVE-2022-45963: Privilege escalation in n/a

> An attacker can bypass privilege restrictions on H3C firewalls to gain elevated access.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 27 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-54hw-8q4q-2g6m

## What is CVE-2022-45963?

CVE-2022-45963 is a critical vulnerability in n/a, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

h3c firewall <= 3.10 ESS6703 has a privilege bypass vulnerability.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 11 products.


Products: H3c Secpath F100-C-G3 Firmware, H3c Secpath F500-6gw Firmware, H3c Secpath F5010 Firmware, H3c Secpath F5020 Firmware, H3c Secpath F5030-D Firmware, H3c Secpath F5030 Firmware, H3c Secpath F5040 Firmware, H3c Secpath F5060-D Firmware, H3c Secpath F5060 Firmware, H3c Secpath F5080-D Firmware, H3c Secpath F5080 Firmware.

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

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

## Is CVE-2022-45963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45963 is a critical vulnerability in n/a, published on 27 Dec 2022. 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-2022-45963 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-2022-45963/ (Markdown: https://insights.sbomify.com/CVE-2022-45963/index.md)
```

## Sources

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

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