dbcve.org
Atp100 FirmwareOperating system · Zyxel

CVE-2022-38547

HIGH · 7.2 CVSS v3.1 Published 2023-02-07
Fix available
A fix is available. Upgrade to after 5.32 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 post-authentication command injection vulnerability in the CLI command of Zyxel ZyWALL/USG series firmware versions 4.20 through 4.72, VPN series firmware versions 4.30 through 5.32, USG FLEX series firmware versions 4.50 through 5.32, and ATP series firmware versions 4.32 through 5.32, which could allow an authenticated attacker with administrator privileges to execute OS commands.

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

A post-authentication command injection vulnerability exists in the CLI command interface of Zyxel ZyWALL/USG, VPN, USG FLEX, and ATP series firewall appliances. An authenticated attacker with administrator privileges can inject and execute arbitrary OS commands through the CLI, gaining full system control.

MitigationUpdate firmware to versions beyond 4.72 (ZyWALL/USG), 5.32 (VPN/USG FLEX/ATP) as specified by Zyxel's security advisories. Additionally, restrict administrative access to trusted IPs only and enforce least-privilege administrator accounts.

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
Atp100 FirmwareOperating system
Affected:>= 4.32, <= 5.32
Atp200 FirmwareOperating system
Affected:>= 4.32, <= 5.32
Atp700 FirmwareOperating system
Affected:>= 4.32, <= 5.32
Atp500 FirmwareOperating system
Affected:>= 4.32, <= 5.32
Atp100w FirmwareOperating system
Affected:>= 4.32, <= 5.32
Atp800 FirmwareOperating system
Affected:>= 4.32, <= 5.32
Usg Flex 50 FirmwareOperating system
Affected:>= 4.50, <= 5.32
Usg Flex 200 FirmwareOperating system
Affected:>= 4.50, <= 5.32

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 management interface or CLI and determine the exact model number (e.g., ATP100, ATP200, ATP500, ATP700, ATP800, USG Flex 50, USG Flex 200)
    Affected if The device is one of the ATP series or USG FLEX models listed in the affected products
  2. Check the firmware version
    In the web interface, go to Maintenance > Firmware or use the CLI command 'show system-info' to retrieve the current firmware version
    Affected if The firmware version falls within 4.32 to 5.32 (for ATP series) or 4.50 to 5.32 (for USG FLEX)
  3. Verify CLI administrator access exists
    Confirm that the CLI interface is accessible and that administrator-level accounts are configured. Check if remote CLI access (SSH/Telnet) is enabled under the system settings
    Affected if The vulnerability is exploitable only by an authenticated administrator with CLI access - if no admin accounts exist or CLI is disabled, the attack surface is reduced

The environment is affected if the device is an ATP series (firmware 4.32-5.32) or USG FLEX 50/200 (firmware 4.50-5.32) and the CLI interface is accessible with administrator credentials.

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 a release after 5.32
Interim mitigation

Update firmware to versions beyond 4.72 (ZyWALL/USG), 5.32 (VPN/USG FLEX/ATP) as specified by Zyxel's security advisories. Additionally, restrict administrative access to trusted IPs only and enforce least-privilege administrator accounts.

Recommended fix Moderate confidence

Firmware version > 5.32 (check Zyxel support for exact latest stable release)

  1. 1. Identify the specific device model (ATP100, ATP200, ATP500, ATP700, ATP100w, ATP800, USG Flex 50, or USG Flex 200) from the affected list
  2. 2. Access the device's web management interface or CLI with administrator credentials
  3. 3. Navigate to the firmware upgrade section (typically under Maintenance > Firmware or System > File Manager)
  4. 4. Download the latest firmware version from Zyxel's official support website (www.zyxel.com/support) for your specific model
  5. 5. Upload and apply the firmware upgrade to the device
  6. 6. After reboot, verify the firmware version has been updated successfully
  7. 7. Confirm the device is functioning normally post-upgrade
Caveat Review Zyxel release notes for any configuration or feature changes between your current version and the new version; backup configuration before upgrading

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

Fix this in Atp100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2022-38547 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