# CVE-2022-45778: Auth bypass in n/a

> An attacker can bypass authentication to gain super administrator privileges on Hillstone Firewalls via a configuration error in report.m.

- **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:** 14 Apr 2025
- **Also known as:** GHSA-h9fm-vg9q-642c

## What is CVE-2022-45778?

CVE-2022-45778 is a critical authentication bypass 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

https://www.hillstonenet.com.cn/ Hillstone Firewall SG-6000 <= 5.0.4.0 is vulnerable to Incorrect Access Control. There is a permission bypass vulnerability in the Hillstone WEB application firewall. An attacker can enter the background of the firewall with super administrator privileges through a configuration error in report.m.

Weakness: CWE-284 (Improper Access Control)

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

It affects 4 products.


Products: Hillstonenet Sc-6000-Wv02 Firmware, Hillstonenet Sc-6000-Wv04 Firmware, Hillstonenet Sc-6000-Wv08 Firmware, Hillstonenet Sc-6000-Wv12 Firmware.

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

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

## Is CVE-2022-45778 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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