CVE-2024-42059
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 post-authentication command injection vulnerability in Zyxel ATP series firmware versions from V5.00 through V5.38, USG FLEX series firmware versions from V5.00 through V5.38, USG FLEX 50(W) series firmware versions from V5.00 through V5.38, and USG20(W)-VPN series firmware versions from V5.00 through V5.38 could allow an authenticated attacker with administrator privileges to execute some OS commands on an affected device by uploading a crafted compressed language file via FTP.
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 post-authentication command injection vulnerability exists in multiple Zyxel firewall series (ATP, USG FLEX, USG FLEX 50W, USG20W-VPN) allowing authenticated administrators to execute arbitrary OS commands by uploading a crafted compressed language file via FTP. The vulnerability stems from insufficient validation of the language file content during the FTP upload process.
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.39CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Zyxel device modelAccess the device web interface or CLI and check the model name (ATP, USG FLEX, USG FLEX 50W, or USG20W-VPN)Affected if Device is one of the listed models and firmware version is between 5.00 and 5.38 inclusive
-
Check firmware versionIn the web interface, go to Maintenance > Firmware or use CLI command 'show system-info' to identify the Zld firmware versionAffected if Firmware version is >= 5.00 and < 5.39 (versions 5.00 through 5.38 are affected)
-
Verify FTP service is enabledIn the web interface, go to Configuration > System > FTP or use CLI to check if FTP server is active (command 'show ftp' or similar)Affected if FTP server is enabled and accessible, as this is the required attack vector
-
Check administrator account accessIn the web interface, go to Configuration > Object > User/Group or CLI 'show admin-user' to list administrator accountsAffected if Any administrator account exists with FTP upload capability, as authentication is required for the exploit
The device is vulnerable if it is a Zyxel ATP, USG FLEX, USG FLEX 50W, or USG20W-VPN running Zld firmware version 5.00 through 5.38, has FTP service enabled, and has an administrator account that can upload language files via FTP.
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.39
Update firmware to a version beyond V5.38. If immediate patching is not possible, restrict FTP access to trusted management networks and limit administrator accounts to only those requiring device management capabilities.
Firmware V5.39 or later for ATP, USG FLEX, USG FLEX 50(W), and USG20(W)-VPN series
- 1. Log into the Zyxel device web management interface as an administrator
- 2. Navigate to the Firmware/System section to check the current firmware version
- 3. Download the firmware version V5.39 or later from the official Zyxel support website (www.zyxel.com/support/download.shtml)
- 4. Use the device's firmware upgrade function to upload and install the new firmware file
- 5. After the upgrade completes, verify the device is running firmware version V5.39 or later
- 6. Confirm the device is functioning normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42059 — 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-2024-42059 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