CVE-2022-2030· NVD / CVE Program· CNA Zyxel

A directory traversal vulnerability caused by specific character sequences within an improperly sanitized URL was identified in some CGI pro

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.3% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; 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

A directory traversal vulnerability caused by specific character sequences within an improperly sanitized URL was identified in some CGI programs of Zyxel USG FLEX 100(W) firmware versions 4.50 through 5.30, USG FLEX 200 firmware versions 4.50 through 5.30, USG FLEX 500 firmware versions 4.50 through 5.30, USG FLEX 700 firmware versions 4.50 through 5.30, USG FLEX 50(W) firmware versions 4.16 through 5.30, USG20(W)-VPN firmware versions 4.16 through 5.30, ATP series firmware versions 4.32 through 5.30, VPN series firmware versions 4.30 through 5.30, USG/ZyWALL series firmware versions 4.11 through 4.72, that could allow an authenticated attacker to access some restricted files on a vulnerable device.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Path traversal

BDU:2022-05403

Published: Jul 19, 2022
Updated: Jun 17, 2026
EPSS: 1.3% · 71th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

CNA vs NVD score

NVD: 6.5
CNA · Zyxel: 6.5; 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
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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	usg flex 100w firmware	cpe:2.3:o:zyxel:usg_flex_100w_firmware
zyxel	usg flex 100w	cpe:2.3:h:zyxel:usg_flex_100w
zyxel	usg flex 200 firmware	cpe:2.3:o:zyxel:usg_flex_200_firmware
zyxel	usg flex 200	cpe:2.3:h:zyxel:usg_flex_200
zyxel	usg flex 500 firmware	cpe:2.3:o:zyxel:usg_flex_500_firmware
zyxel	usg flex 500	cpe:2.3:h:zyxel:usg_flex_500
zyxel	usg flex 700 firmware	cpe:2.3:o:zyxel:usg_flex_700_firmware
zyxel	usg flex 700	cpe:2.3:h:zyxel:usg_flex_700
zyxel	usg flex 50w firmware	cpe:2.3:o:zyxel:usg_flex_50w_firmware
zyxel	usg flex 50w	cpe:2.3:h:zyxel:usg_flex_50w
zyxel	usg20w-vpn firmware	cpe:2.3:o:zyxel:usg20w-vpn_firmware
zyxel	usg20w-vpn	cpe:2.3:h:zyxel:usg20w-vpn

and 38 more

Affected versions

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.30 inclusive
zyxel atp100w firmware4.32 and later · up to 5.30 inclusive
zyxel atp200 firmware4.32 and later · up to 5.30 inclusive
zyxel atp500 firmware4.32 and later · up to 5.30 inclusive
zyxel atp700 firmware4.32 and later · up to 5.30 inclusive
zyxel atp800 firmware4.32 and later · up to 5.30 inclusive
zyxel usg 2200-vpn firmware4.30 and later · up to 5.30 inclusive
zyxel usg flex 100w firmware4.50 and later · up to 5.30 inclusive
zyxel usg flex 200 firmware4.50 and later · up to 5.30 inclusive
zyxel usg flex 500 firmware4.50 and later · up to 5.30 inclusive
zyxel usg flex 50w firmware4.20 and later · up to 5.30 inclusive
zyxel usg flex 700 firmware4.50 and later · up to 5.30 inclusive
zyxel usg20-vpn firmware4.30 and later · up to 5.30 inclusive
zyxel usg20w-vpn firmware4.20 and later · up to 5.30 inclusive
zyxel usg40 firmware4.20 and later · up to 4.72 inclusive
zyxel usg40w firmware4.20 and later · up to 4.72 inclusive
zyxel usg60 firmware4.20 and later · up to 4.72 inclusive
zyxel usg60w firmware4.20 and later · up to 4.72 inclusive
zyxel vpn100 firmware4.30 and later · up to 5.30 inclusive
zyxel vpn1000 firmware4.30 and later · up to 5.30 inclusive

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.30affected
Zyxel USG 20(W)-VPN firmware
- 4.16 through 5.30affected
Zyxel USG FLEX 100(W) firmware
- 4.50 through 5.30affected
Zyxel USG FLEX 200 firmware
- 4.50 through 5.30affected
Zyxel USG FLEX 50(W) firmware
- 4.16 through 5.30affected
Zyxel USG FLEX 500 firmware
- 4.50 through 5.30affected
Zyxel USG FLEX 700 firmware
- 4.50 through 5.30affected
Zyxel USG/ZyWALL series firmware
- 4.11 through 4.72affected
Zyxel VPN series firmware
- 4.30 through 5.30affected

Same product

zyxel: all records

Other highest-scoring records for the same primary product.

CVE-2022-30525A OS command injection vulnerability in the CGI program of Zyxel USG FLEX 100(W) firmware versions 5.00 through 5.21 Patch 1, USG FLEX 200 fKEV
99Now
CVE-2022-30526A privilege escalation vulnerability was identified in the CLI command of Zyxel USG FLEX 100(W) firmware versions 4.50 through 5.30, USG FLE
40Plan

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

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

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)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.zyxel.com/support/Zyxel-security-advisory-authenticated-directory-traversal-vulnerabilities-of-firewalls.shtml

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records