CVE-2023-28767
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 · uneditedThe configuration parser fails to sanitize user-controlled input in the Zyxel ATP series firmware versions 5.10 through 5.36, USG FLEX series firmware versions 5.00 through 5.36, USG FLEX 50(W) series firmware versions 5.10 through 5.36, USG20(W)-VPN series firmware versions 5.10 through 5.36, and VPN series firmware versions 5.00 through 5.36. An unauthenticated, LAN-based attacker could leverage the vulnerability to inject some operating system (OS) commands into the device configuration data on an affected device when the cloud management mode is enabled.
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 configuration parser of multiple Zyxel firewall series (ATP, USG FLEX, USG20W-VPN, VPN). The parser fails to sanitize user-controlled input, allowing an unauthenticated LAN-based attacker to inject OS commands into device configuration when cloud management mode is enabled.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Zyxel device modelAccess the device web interface under Status or Dashboard, or run CLI command 'show system-info' to confirm the exact model name (e.g., USG Flex 200, ATP series)Affected if Model is not one of the listed affected products (USG 2200 VPN, USG Flex 100/100w/200/50/50w/500/700)
-
Check the installed firmware versionIn the web interface go to Maintenance > Firmware or use CLI command 'show version' to retrieve the firmware version numberAffected if Firmware version is 5.00 through 5.36 (inclusive) - versions below 5.00 are not affected, 5.37 and above are patched
-
Verify cloud management mode statusIn the web interface navigate to CONFIGURATION > Cloud Management or use CLI command 'show cloud-management status' to determine if cloud management is enabledAffected if Cloud management mode is turned ON - this is the required condition for the command injection to be exploitable
A device is affected only if it is one of the listed models, runs firmware version 5.00 through 5.36, AND has cloud management mode enabled.
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
Disable cloud management mode if not required and update firmware to a patched version beyond 5.36. Restrict LAN access to trusted users only as an interim compensating control.
Firmware version 5.37 or later (e.g., 5.37, 5.38, or latest stable release)
- 1. Identify the exact Zyxel device model (USG 2200 VPN, USG Flex 100, USG Flex 100w, USG Flex 200, USG Flex 50, USG Flex 500, USG Flex 50w, or USG Flex 700)
- 2. Access the device administration interface and check the current firmware version under Status or System Info
- 3. Navigate to the official Zyxel support website (www.zyxel.com) and locate the firmware download section for your specific device model
- 4. Download firmware version 5.37 or later (the first fixed release) for your device
- 5. In the device admin panel, go to Maintenance > Firmware Upgrade or similar section
- 6. Upload the downloaded firmware file and initiate the upgrade process
- 7. Wait for the upgrade to complete and the device to reboot
- 8. Verify the new firmware version is installed and the device is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28767 — 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-28767 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