Cyber Resilience

CVE-2022-0342

Auth Bypass in Zyxel Nsg300 Firmware 1.20 – 1.33

High EPSSAuth Bypass
Published
28 March 2022
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.84 99.7th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2022-0342 is a critical-severity Improper Authentication (CWE-287) vulnerability in Zyxel Nsg300 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-2 (Identification and Authentication (Organizational Users)) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

An authentication bypass vulnerability tracked as CVE-2022-0342 affects the CGI program in multiple Zyxel firewall product lines. Impacted firmware includes USG/ZyWALL series versions 4.20 through 4.70, USG FLEX series 4.50 through 5.20, ATP series 4.32 through 5.20, VPN series 4.30 through 5.20, and NSG series V1.20 through V1.33 Patch 4. The flaw, assigned CWE-287 and carrying a CVSS v3.1 score of 9.8, permits an unauthenticated remote attacker to circumvent web authentication controls.

An attacker with network access can exploit the issue without credentials or user interaction to obtain full administrative access to the affected device. Successful exploitation grants the ability to read, modify, or delete configuration and data, fully compromising confidentiality, integrity, and availability of the firewall.

Zyxel published a security advisory detailing the vulnerability and directing customers to apply available firmware updates or configuration mitigations for the listed product families.

The associated EPSS score remains elevated, with a current value of 0.9236 and a peak of 0.9256, indicating sustained exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An authentication bypass vulnerability in the CGI program of Zyxel USG/ZyWALL series firmware versions 4.20 through 4.70, USG FLEX series firmware versions 4.50 through 5.20, ATP series firmware versions 4.32 through 5.20, VPN series firmware versions 4.30 through 5.20, and…

more

NSG series firmware versions V1.20 through V1.33 Patch 4, which could allow an attacker to bypass the web authentication and obtain administrative access of the device.

CWE(s)

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
Unauthenticated remote exploitation of the CGI authentication bypass directly enables access to a public-facing network device.
T1078 Valid Accounts Stealthconfidence: HIGH
Bypassing web authentication grants the attacker valid administrative credentials on the device.
T1133 External Remote Services Persistenceconfidence: HIGH
The flaw allows remote administrative access via the device's exposed management interface without credentials.
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2023-22916Same product: Zyxel Atp100
CVE-2023-22917Same product: Zyxel Atp100
CVE-2022-30525Same product: Zyxel Atp100
CVE-2020-29583Same product: Zyxel Atp100
CVE-2023-27990Same product: Zyxel Atp100
CVE-2023-28771Same product: Zyxel Atp100
CVE-2023-27991Same product: Zyxel Atp100
CVE-2024-11494Same vendor: Zyxel
CVE-2023-35137Same vendor: Zyxel
CVE-2023-33010Same product: Zyxel Atp100

Affected Assets

zyxel
usg40 firmware
4.20 — 4.71
zyxel
usg40w firmware
4.20 — 4.71
zyxel
usg60 firmware
4.20 — 4.71
zyxel
usg60w firmware
4.20 — 4.71
zyxel
zywall 110 firmware
4.20 — 4.71
zyxel
zywall 310 firmware
4.20 — 4.71
zyxel
zywall 1100 firmware
4.20 — 4.71
zyxel
usg flex 100 firmware
4.50 — 5.20
zyxel
usg flex 200 firmware
4.50 — 5.20
zyxel
usg flex 500 firmware
4.50 — 5.20
+13 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • IA-2 Identification and Authentication (Organizational Users)
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.4
  • V6.5.4
  • V6.5.5
  • V6.5.7

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authentication and authorization decisions on the web interface before granting administrative access, blocking the CGI bypass.

prevent

Requires valid identification and authentication of users prior to allowing access to the firewall's management functions, directly countering the unauthenticated bypass.

prevent

Mandates timely application of vendor firmware patches that eliminate the authentication flaw in the affected CGI program.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

PR.AA-03 directly enforces authentication mechanisms that eliminate most improper-authentication defects, yet CWE-287 spans additional vectors (missing checks, flawed protocols, session handling) that one control does not fully close.

PR.AA-04 mostly match
prevents

PR.AA-04 directly enables verification of identity assertions (mostly preventing CWE-287 in that scope) yet leaves many other authentication failure modes unaddressed (only partial prevention overall).

PR.AA-01 partial match
prevents

PR.AA-01 supplies and governs credentials/tokens that authentication relies on, removing some weak-credential cases, yet leaves verification logic, missing checks, and protocol flaws untouched.

PR.AA-02 partial match
prevents

PR.AA-02 ensures valid enrollment and unique credential binding, which reduces some improper-auth risks at issuance time but leaves runtime claim verification untouched, so each direction only partially addresses the other.

PR.PS-01 partial match
prevents

PR.PS-01 can enforce auth-related settings via hardened baselines and default reviews, blocking some config-based instances of CWE-287, yet leaves code-level auth flaws untouched so neither direction reaches mostly.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate some known auth vulnerabilities after deployment (partial forward) but does not address the design or implementation of authentication logic itself (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Requiring authentication methods whose strength matches the sensitivity of the data and mandating multi-factor authentication directly blocks attempts to access resources without proving identity.

prevents

Verifying user identity before issuing replacement credentials and forcing changes after compromise reduces the likelihood that authentication bypass can be achieved through stolen or weak credentials.

prevents

Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.

mitigates

Requiring authentication mechanisms and technical parameters for secure connections ensures that network services verify user identity before granting access, preventing exploitation of missing or weak authentication.

prevents

Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.

prevents

Defining the required level of trust in entity identity and the authentication mechanisms to achieve it ensures that authentication is explicitly addressed rather than omitted.

References