dbcve.org
QtsOperating system · Qnap

CVE-2024-50393

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 command injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.2.2950 build 20241114 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.2.2952 build 20241116 and later

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 command injection vulnerability in QNAP QTS and QuTS hero operating systems allows remote unauthenticated attackers to execute arbitrary commands due to insufficient input validation. The critical severity (CVSS 9.8) indicates network-based exploitation with no user interaction required.

MitigationApply available security patches by upgrading to QTS 5.1.9.2954 build 20241120 / 5.2.2.2950 build 20241114 or QuTS hero h5.1.9.2954 build 20241120 / h5.2.2.2952 build 20241116 or later versions.

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
QtsOperating system
Affected:= 5.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.1.0.2444= 5.1.0.2466= 5.1.1.2491= 5.1.2.2533= 5.1.3.2578= 5.1.4.2596= 5.1.5.2645= 5.1.5.2679= 5.1.6.2722
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.1.0.2424= h5.1.0.2453= h5.1.0.2466= h5.1.1.2488= h5.1.2.2534= h5.1.3.2578= h5.1.4.2596= h5.1.5.2647= h5.1.5.2680= h5.1.6.2734= h5.1.7.2770

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

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify QNAP device and OS type
    Access the QNAP admin dashboard or use `uname -a` via SSH to confirm whether the device runs QTS or QuTS hero
    Affected if Device is a QNAP NAS running QTS or QuTS hero
  2. Check QTS version
    In QTS admin panel, go to Control Panel > System > Firmware Update > Check firmware version, or run `getcfg System.Version` via QCLI
    Affected if Version matches any of these exact builds: 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444, 5.1.0.2466, 5.1.1.2491, 5.1.2.2533, 5.1.3.2578, 5.1.4.2596, 5.1.5.2645, 5.1.5.2679, or 5.1.6.2722
  3. Check QuTS hero version
    In QuTS hero admin panel, go to Control Panel > System > Firmware Update > Check firmware version, or run `getcfg System.Version` via QCLI
    Affected if Version matches any of these exact builds: h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1.2.2534, h5.1.3.2578, h5.1.4.2596, h5.1.5.2647, h5.1.5.2680, h5.1.6.2734, or h5.1.7.2770
  4. Confirm network exposure
    Verify that the QNAP admin interface (ports 8080, 443) is accessible from the network or internet
    Affected if The web management interface is reachable from untrusted networks without VPN filtering

If the installed QTS or QuTS hero version exactly matches any of the listed affected builds and the admin interface is network-accessible, the system is vulnerable to remote command injection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available security patches by upgrading to QTS 5.1.9.2954 build 20241120 / 5.2.2.2950 build 20241114 or QuTS hero h5.1.9.2954 build 20241120 / h5.2.2.2952 build 20241116 or later versions.

Recommended fix High confidence

QTS 5.1.9.2954 (build 20241120) / QTS 5.2.2.2950 (build 20241114) / QuTS hero h5.1.9.2954 (build 20241120) / QuTS hero h5.2.2.2952 (build 20241116) or later

  1. 1. Back up all critical data on the NAS device before proceeding with firmware updates
  2. 2. Identify your current QTS or QuTS hero version via Control Panel > System > Firmware Update > firmware version
  3. 3. Determine the appropriate fixed version based on your current major version: For QTS 5.1.x, upgrade to QTS 5.1.9.2954 (build 20241120) or later; For QTS 5.2.x, upgrade to QTS 5.2.2.2950 (build 20241114) or later; For QuTS hero h5.1.x, upgrade to h5.1.9.2954 (build 20241120) or later; For QuTS hero h5.2.x, upgrade to h5.2.2.2952 (build 20241116) or later
  4. 4. Download the firmware from the official QNAP website (www.qnap.com) or access via the QNAP Control Panel > System > Firmware Update
  5. 5. Apply the firmware update via Control Panel > System > Firmware Update > Check for Update, or manually upload the firmware file if required
  6. 6. Reboot the NAS as prompted after the update completes
  7. 7. Verify the installed firmware version matches or exceeds the fixed version for your product line
Caveat Standard QNAP firmware upgrade risks apply - ensure data backup before updating; some older applications or configurations may require re-validation after major version jumps

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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