dbcve.org
QtsOperating system · Qnap

CVE-2024-32766

CRITICAL · 10.0 CVSS v3.1 Published 2024-04-26
Fix available
A fix is available. Upgrade to 4.5.4.2627 / 5.1.3.2578 or later.
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
An OS command injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to execute commands via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.3.2578 build 20231110 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.3.2578 build 20231110 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 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 · moderate confidence

OS command injection vulnerability in multiple QNAP operating system versions (QTS, QuTS hero, QuTScloud) allowing remote command execution via network with critical severity (CVSS 10).

MitigationUpdate affected QNAP systems to the following patched versions: QTS 5.1.3.2578+ or QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+ or QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+.

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:< 4.5.4.2627>= 5.0.0, < 5.1.3.2578= 4.5.4.2627= 5.1.3.2578
Quts HeroOperating system
Affected:>= h4.5.0, < h4.5.4.2626>= h5.0.0, < h5.1.3.2578= h4.5.4.2626= h5.1.3.2578
QutscloudOperating system
Affected:>= c5.0.0.1919, < c5.1.5.2651

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 product type and version
    Log into QTS/QuTS hero/QuTScloud admin interface and navigate to Control Panel > System > System Information, or run command: cat /etc/config/default/si_system.conf
    Affected if Version is QTS < 4.5.4.2627 or = 4.5.4.2627 or = 5.1.3.2578 or >= 5.0.0, < 5.1.3.2578; OR QuTS hero < h4.5.4.2626 or = h4.5.4.2626 or = h5.1.3.2578 or >= h5.0.0, < h5.1.3.2578; OR QuTScloud >= c5.0.0.1919, < c5.1.5.2651
  2. Confirm myQNAPcloud Linktoservice is enabled
    In QTS admin, go to myQNAPcloud > Linktoservice and check if the service is turned on; or check config file: /etc/config/qnap/qnap_config.xml for Linktoservice status
    Affected if Linktoservice feature is enabled on the device
  3. Verify PHP modules are present
    Run command: php -m | grep -E '(xml|simplexml)' to list loaded PHP modules
    Affected if PHP with SimpleXML/XML processing is available on the system (required for the vulnerable code path to execute)

A user is affected if their QNAP device runs QTS, QuTS hero, or QuTScloud in any of the vulnerable version ranges AND has the myQNAPcloud Linktoservice feature enabled.

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 4.5.4.2627 / 5.1.3.2578 or later
Fixed in 4.5.4.26275.1.3.2578
Interim mitigation

Update affected QNAP systems to the following patched versions: QTS 5.1.3.2578+ or QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+ or QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+.

Recommended fix High confidence

QTS 4.5.4.2627 (build 20231225+) or QTS 5.1.3.2578 (build 20231110+); QuTS hero h4.5.4.2626 (build 20231225+) or h5.1.3.2578 (build 20231110+); QuTScloud c5.1.5.2651+

  1. 1. Identify the QNAP device model and current QTS/QuTS hero/QuTScloud version via System Settings > System Information
  2. 2. Navigate to App Center or Control Panel > System > Firmware Update
  3. 3. Check for available updates and upgrade to the appropriate fixed version: For QTS systems: upgrade to version 4.5.4.2627 build 20231225 or later, or 5.1.3.2578 build 20231110 or later; For QuTS hero systems: upgrade to version h4.5.4.2626 build 20231225 or later, or h5.1.3.2578 build 20231110 or later; For QuTScloud: upgrade to version c5.1.5.2651 or later
  4. 4. After upgrade, verify the system is running a fixed version by checking System > System Information
  5. 5. Ensure the device is not directly exposed to the internet and implement network segmentation as a defense-in-depth measure
Caveat Review QNAP release notes for any breaking changes or deprecated features in the target version before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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