CVE-2022-0342: An authentication bypass vulnerability in the CGI program of Zyxel USG/ZyWALL series firmware versions 4.20 through 4.70, USG FLEX series…
Noroxi assessment
Priority: This week (action score 68/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 95.1% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 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.
- Published
- Mar 28, 2022
- Updated
- Jun 17, 2026
- EPSS
- 95.1% · 99th percentile
- CWE
- CWE-287
Report tools
Action score
68
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 29 / 30 · 95.1%
CNA vs NVD score
- NVD
- 9.8
- CNA · Zyxel
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zyxel | usg40 firmware | cpe:2.3:o:zyxel:usg40_firmware |
| zyxel | usg40 | cpe:2.3:h:zyxel:usg40 |
| zyxel | usg40w firmware | cpe:2.3:o:zyxel:usg40w_firmware |
| zyxel | usg40w | cpe:2.3:h:zyxel:usg40w |
| zyxel | usg60 firmware | cpe:2.3:o:zyxel:usg60_firmware |
| zyxel | usg60 | cpe:2.3:h:zyxel:usg60 |
| zyxel | usg60w firmware | cpe:2.3:o:zyxel:usg60w_firmware |
| zyxel | usg60w | cpe:2.3:h:zyxel:usg60w |
| zyxel | zywall 110 firmware | cpe:2.3:o:zyxel:zywall_110_firmware |
| zyxel | zywall 110 | cpe:2.3:h:zyxel:zywall_110 |
| zyxel | zywall 310 firmware | cpe:2.3:o:zyxel:zywall_310_firmware |
| zyxel | zywall 310 | cpe:2.3:h:zyxel:zywall_310 |
and 34 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zyxel). Independent of NVD's CPE analysis and usually ahead of it.
Zyxel ATP series firmware
- 4.32 through 5.20affected
Zyxel NSG series firmware
- 1.20 through 1.33 Patch 4affected
Zyxel USG FLEX series firmware
- 4.50 through 5.20affected
Zyxel USG/ZyWALL series firmware
- 4.20 through 4.70affected
Zyxel VPN series firmware
- 4.30 through 5.20affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zyxel atp100 firmware4.32 and later · up to 5.20 inclusive
- zyxel atp100w firmware4.32 and later · up to 5.20 inclusive
- zyxel atp200 firmware4.32 and later · up to 5.20 inclusive
- zyxel atp500 firmware4.32 and later · up to 5.20 inclusive
- zyxel atp700 firmware4.32 and later · up to 5.20 inclusive
- zyxel atp800 firmware4.32 and later · up to 5.20 inclusive
- zyxel nsg300 firmware1.20 and later · before 1.33
- zyxel nsg300 firmware1.33
- zyxel usg flex 100 firmware4.50 and later · up to 5.20 inclusive
- zyxel usg flex 100w firmware4.50 and later · up to 5.20 inclusive
- zyxel usg flex 200 firmware4.50 and later · up to 5.20 inclusive
- zyxel usg flex 500 firmware4.50 and later · up to 5.20 inclusive
- zyxel usg flex 700 firmware4.50 and later · up to 5.20 inclusive
- zyxel usg40 firmware4.20 and later · before 4.71
- zyxel usg40w firmware4.20 and later · before 4.71
- zyxel usg60 firmware4.20 and later · before 4.71
- zyxel usg60w firmware4.20 and later · before 4.71
- zyxel vpn100 firmware4.30 and later · before 5.21
- zyxel vpn1000 firmware4.30 and later · before 5.21
- zyxel vpn300 firmware4.30 and later · before 5.21
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2022-0342 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0280 · Apr 4, 2022(Zyxel Güvenlik Güncellemesi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.