dbcve.org
ZldOperating system · Zyxel

CVE-2024-42060

HIGH · 7.2 CVSS v3.1 Published 2024-09-03
Fix available
A fix is available. Upgrade to 5.39 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 Zyxel ATP series firmware versions from V4.32 through V5.38, USG FLEX series firmware versions from V4.50 through V5.38, USG FLEX 50(W) series firmware versions from V4.16 through V5.38, and USG20(W)-VPN series firmware versions from V4.16 through V5.38 could allow an authenticated attacker with administrator privileges to execute some OS commands on an affected device by uploading a crafted internal user agreement file to the vulnerable 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

A post-authentication command injection vulnerability in Zyxel ATP, USG FLEX, and USG20(W)-VPN firewall series allows an authenticated administrator to execute OS commands by uploading a crafted internal user agreement file containing malicious payload to the affected device.

MitigationUpdate firmware to a version beyond V5.38 for all affected product series. Until patched, limit administrator access, monitor for unauthorized file uploads, and review administrative activity logs.

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
ZldOperating system
Affected:>= 4.32, < 5.39>= 4.50, < 5.39>= 4.16, < 5.39

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 your Zyxel device model
    Access the device web GUI or CLI and retrieve the exact model name from the dashboard or system information page
    Affected if The model is NOT one of: ATP series, USG FLEX series, or USG20(W)-VPN series (if it is one of these, continue to next check)
  2. Check the installed firmware version
    In the web GUI, go to Maintenance > Firmware > Firmware Upgrade or use CLI command 'show version' to retrieve the current firmware version
    Affected if The firmware version is 4.16 or higher but lower than 5.39 (versions 4.16 <= version < 5.39 are affected)
  3. Verify administrator access to user agreement upload feature
    Log into the device as an administrator and navigate to the user agreement or customization settings (typically under Object > User or Configuration > Object settings in the web GUI)
    Affected if An authenticated administrator account has access to upload or import internal user agreement files on the device
  4. Review admin activity logs for file upload events
    Check the device logs under Monitor > Log or System > Log for entries containing file upload operations, especially those related to user agreement or customization files
    Affected if You find upload events for user agreement files from accounts you do not recognize or did not initiate

You are affected if your device is a Zyxel ATP, USG FLEX, or USG20(W)-VPN model running firmware version 4.16 or higher but lower than 5.39, and an authenticated administrator can access the internal user agreement upload feature.

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.39 or later
Fixed in 5.39
Interim mitigation

Update firmware to a version beyond V5.38 for all affected product series. Until patched, limit administrator access, monitor for unauthorized file uploads, and review administrative activity logs.

Recommended fix Moderate confidence

Firmware version 5.39 or later (latest stable release for the specific model)

  1. 1. Identify the specific Zyxel device model (ATP series, USG FLEX series, USG FLEX 50W, or USG20W-VPN) that needs remediation.
  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 the official Zyxel support website (www.zyxel.com/support) for the specific device model.
  5. 5. Upload and apply the firmware version 5.39 or later.
  6. 6. After upgrade, verify the device is functioning normally and confirm the new firmware version is applied.
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and plan for brief downtime; review release notes for any configuration changes

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

Fix this in Zld Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42060 — 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-2024-42060 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