CVE-2023-34141
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 · uneditedA command injection vulnerability in the access point (AP) management feature of the Zyxel ATP series firmware versions 5.00 through 5.36 Patch 2, USG FLEX series firmware versions 5.00 through 5.36 Patch 2, USG FLEX 50(W) series firmware versions 5.00 through 5.36 Patch 2, USG20(W)-VPN series firmware versions 5.00 through 5.36 Patch 2, VPN series firmware versions 5.00 through 5.36 Patch 2, NXC2500 firmware versions 6.10(AAIG.0) through 6.10(AAIG.3), and NXC5500 firmware versions 6.10(AAOS.0) through 6.10(AAOS.4), could allow an unauthenticated, LAN-based attacker to execute some OS commands on an affected device if the attacker could trick an authorized administrator to add their IP address to the managed AP list in advance.
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 confidenceA command injection vulnerability exists in the AP management feature of multiple Zyxel security appliance series. An unauthenticated LAN-based attacker can execute OS commands by first tricking an administrator to add the attacker's IP address to the managed AP list, then leveraging the command injection in the AP management functionality.
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>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37>= 5.00, < 5.37CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelDetermine the exact model number of the Zyxel security appliance. This vulnerability affects only the following models: USG 20w VPN, USG 2200 VPN, USG Flex 100, USG Flex 100w, USG Flex 200, USG Flex 50, USG Flex 50w, and USG Flex 500.Affected if The device is one of the listed affected models.
-
Check the installed firmware versionAccess the device administrative interface or use the CLI command to retrieve the current firmware version. Compare it against the vulnerable range: version 5.00 or later but earlier than version 5.37.Affected if The firmware version falls within >= 5.00 and < 5.37.
-
Verify if AP management feature is enabledCheck the device configuration to determine whether the AP management (Access Point management) feature is turned on. This is typically found in the wireless or AP management settings section of the web interface or via CLI.Affected if AP management feature is enabled and configured on the device.
-
Inspect the managed AP listReview the list of configured managed AP IP addresses in the device configuration. Look for any AP entries that point to IP addresses you do not recognize or did not intentionally add.Affected if The managed AP list contains unexpected or unauthorized IP addresses that were not added by a legitimate administrator.
The device is affected if it is one of the affected USG models, runs firmware version 5.00 through 5.36.x, has AP management enabled, and has an unrecognized IP address in its managed AP list.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.37
Apply vendor firmware updates to all affected devices (5.36 Patch 3 or later for most series). Until patched, strictly limit LAN access and verify the legitimacy of any AP IP addresses before adding them to the managed AP list.
5.37 or later
- Download the latest firmware version 5.37 or later from the official Zyxel support website (www.zyxel.com) for your specific device model
- Access the device web management interface or use the command-line interface
- Upload and install the firmware version 5.37 or later
- After installation, verify the firmware version has been successfully updated
- Restart the device if required to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34141 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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