Usg 2200 Vpn FirmwareOperating system · Zyxel

CVE-2023-34139

HIGH · 8.8 CVSS v3.1 Published 2023-07-17
Fix available
A fix is available. Upgrade to 5.37 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A command injection vulnerability in the Free Time WiFi hotspot feature of the Zyxel USG FLEX series firmware versions 4.50 through 5.36 Patch 2 and VPN series firmware versions 4.20 through 5.36 Patch 2, could allow an unauthenticated, LAN-based attacker to execute some OS commands on an affected device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in the Free Time WiFi hotspot feature of Zyxel USG FLEX and VPN series firewalls. An unauthenticated attacker on the LAN can execute arbitrary OS commands due to insufficient input sanitization in the hotspot feature.

MitigationApply the latest Zyxel firmware patch beyond version 5.36 Patch 2. Until patched, restrict LAN access to untrusted users and segment guest WiFi networks from management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Usg 2200 Vpn FirmwareOperating system
Affected:>= 4.20, < 5.37
Usg Flex 100 FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 100w FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 200 FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 50 FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 500 FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 50w FirmwareOperating system
Affected:>= 4.50, < 5.37
Usg Flex 700 FirmwareOperating system
Affected:>= 4.50, < 5.37

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the web GUI (System > Status) or run 'show system-info' via CLI to confirm the exact model (USG 2200 VPN, USG Flex 100, 100w, 200, 50, 50w, 500, or 700)
    Affected if Model is NOT one of these eight affected models
  2. Check the firmware version
    In web GUI go to Maintenance > Firmware or run 'show system-info' via CLI to view the running firmware version
    Affected if Version is >= 4.20 (for USG 2200 VPN) or >= 4.50 (for USG Flex models) AND version is < 5.37
  3. Verify if Free Time WiFi hotspot is enabled
    In web GUI navigate to Configuration > Hotspot > Free Time or check the hotspot service status via CLI (show hotspot or related command)
    Affected if Free Time WiFi hotspot feature is currently enabled and configured on the device

The device is affected if it is a USG 2200 VPN, USG Flex 100/100w/200/50/50w/500/700 model running firmware version 4.20+ (or 4.50+) but below 5.37 AND the Free Time WiFi hotspot feature is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.37 or later
Fixed in 5.37
Interim mitigation

Apply the latest Zyxel firmware patch beyond version 5.36 Patch 2. Until patched, restrict LAN access to untrusted users and segment guest WiFi networks from management interfaces.

Recommended fix High confidence

Firmware version 5.37

  1. Identify the specific model number of the Zyxel USG FLEX or USG VPN device
  2. Backup the current device configuration through the web interface or CLI
  3. Navigate to Zyxel's official support website (www.zyxel.com) and locate the firmware download section
  4. Download firmware version 5.37 for the specific device model
  5. Access the device's web management interface and navigate to Maintenance > Firmware Upgrade
  6. Upload the downloaded firmware file (5.37) and initiate the upgrade process
  7. Wait for the device to reboot and apply the firmware (this may take several minutes)
  8. Verify the firmware version has been updated to 5.37 in the device status

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Usg 2200 Vpn Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34139 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data