# CVE-2022-33202: Auth bypass in L2Blocker

> An adjacent attacker can bypass authentication on the L2Blocker setup screen to access stored information or cause device malfunction.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mh3g-wmcq-xxrw

## What is CVE-2022-33202?

CVE-2022-33202 is a high-severity authentication bypass vulnerability in SOFTCREATE CORP. L2Blocker, published on 27 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication bypass vulnerability in the setup screen of L2Blocker(on-premise) Ver4.8.5 and earlier and L2Blocker(Cloud) Ver4.8.5 and earlier allows an adjacent attacker to perform an unauthorized login and obtain the stored information or cause a malfunction of the device by using alternative paths or channels for Sensor.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Softcreate L2blocker.

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

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

## Is CVE-2022-33202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33202 is a high-severity authentication bypass vulnerability in SOFTCREATE CORP. L2Blocker, published on 27 Jun 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-33202 in the wild and no public exploit code.

Affected product: SOFTCREATE CORP. L2Blocker. 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-33202/ (Markdown: https://insights.sbomify.com/CVE-2022-33202/index.md)
```

## Sources

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

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