Authentication bypass vulnerability in the setup screen of L2Blocker(on-premise) Ver4.8.5 and earlier and L2Blocker(Cloud) Ver4.8.5 and ear…

published 2022-06-27 4y ago modified 2026-06-17 4mo ago also EUVD-2022-36245

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

softcreate l2blocker 4.8.6

Is CVE-2022-33202 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	4.8	AV:A/AC:L/Au:N/C:P/I:P/A:N

Affected products

SOFTCREATE CORP. L2Blocker

Classification

Weakness

CWE-287 Improper Authentication

References

softcreate.co.jp /news/detail/210
vendor-advisory
jvn.jp /en/jp/JVN51464799/index.html
third-party-advisory

Sources

CVE List CVE-2022-33202
NVD CVE-2022-33202

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.