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

> Attackers can brute force admin passwords due to missing rate limits, leading to full account takeover of the network firewall.

- **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:** 12 Oct 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-c4hc-pv5q-j9xp

## What is CVE-2022-33106?

CVE-2022-33106 is a critical authentication bypass vulnerability in n/a, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WiJungle NGFW Version U250 was discovered to be vulnerable to No Rate Limit attack, allowing the attacker to brute force the admin password leading to Account Take Over.

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

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

It affects 1 product.


Products: Wijungle U250 Firmware.

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

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

## Is CVE-2022-33106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33106 is a critical authentication bypass vulnerability in n/a, published on 12 Oct 2022. 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-33106 exists.

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-33106/ (Markdown: https://insights.sbomify.com/CVE-2022-33106/index.md)
```

## Sources

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

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