dbcve.org
QtsApplication · Qnap

CVE-2021-44051

HIGH · 8.8 CVSS v3.1 Published 2022-05-05
Fix available
A fix is available. Upgrade to 4.3.3.1945 / 4.3.4.1976 or later.
See remediation →
94/100
Remediation priority · Urgent
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 command injection vulnerability has been reported to affect QNAP NAS running QuTScloud, QuTS hero and QTS. If exploited, this vulnerability allows remote attackers to run arbitrary commands. We have already fixed this vulnerability in the following versions of QuTScloud, QuTS hero and QTS: QuTScloud c5.0.1.1949 and later QuTS hero h5.0.0.1986 build 20220324 and later QTS 5.0.0.1986 build 20220324 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

Command injection vulnerability in QNAP NAS devices running QuTScloud, QuTS hero, and QTS allows remote attackers to execute arbitrary commands on the affected system.

MitigationUpgrade affected QNAP NAS devices to the patched versions: QuTScloud c5.0.1.1949 or later, QuTS hero h5.0.0.1986 build 20220324 or later, or QTS 5.0.0.1986 build 20220324 or later.

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
QtsApplication
Affected:>= 5.0.0.1716, < 5.0.0.1986>= 4.3.3.0174, < 4.3.3.1945>= 4.3.4.0899, < 4.3.4.1976>= 4.3.6.0895, < 4.3.6.1965>= 4.4.0.0883, < 4.5.4.1991= 4.2.6
Quts HeroOperating system
Affected:< h4.5.4.1771>= h5.0.0.1772, < h5.0.0.1986
QutscloudOperating system
Affected:< c5.0.1.1998

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the QNAP NAS product model
    Log into the QNAP admin console and locate the System Information or System Status page to identify whether the device runs QTS, QuTS hero, or QuTScloud
    Affected if The device is running QTS, QuTS hero, or QuTScloud and the specific version falls within the affected ranges
  2. Check the installed QTS version
    Navigate to Control Panel > System > System Status > Firmware Version, or use the command `cat /etc/config/def_boot` to view the firmware version
    Affected if The installed version is >= 5.0.0.1716 and < 5.0.0.1986; OR >= 4.3.3.0174 and < 4.3.3.1945; OR >= 4.3.4.0899 and < 4.3.4.1976; OR >= 4.3.6.0895 and < 4.3.6.1965; OR >= 4.4.0.0883 and < 4.5.4.1991; OR equals 4.2.6
  3. Check the installed QuTS hero version
    Navigate to Control Panel > System > System Status > Firmware Version to view the QuTS hero build number, typically denoted with an 'h' prefix
    Affected if The installed version is < h4.5.4.1771; OR >= h5.0.0.1772 and < h5.0.0.1986
  4. Check the installed QuTScloud version
    Access the QuTScloud System Information page in the admin console or check the cloud instance metadata for the build version typically prefixed with 'c'
    Affected if The installed version is < c5.0.1.1998

The system is affected if it runs QTS, QuTS hero, or QuTScloud and its specific firmware version matches any of the affected version ranges listed for that product.

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.3.3.1945 / 4.3.4.1976 / 4.3.6.1965 or later
Fixed in 4.3.3.19454.3.4.19764.3.6.1965
Interim mitigation

Upgrade affected QNAP NAS devices to the patched versions: QuTScloud c5.0.1.1949 or later, QuTS hero h5.0.0.1986 build 20220324 or later, or QTS 5.0.0.1986 build 20220324 or later.

Recommended fix High confidence

QTS 5.0.0.1986 (build 20220324+); QuTS Hero h5.0.0.1986 (build 20220324+) or h4.5.4.1771+; QuTScloud c5.0.1.1998+

  1. 1. Identify the QNAP NAS product model and current firmware version (QTS, QuTS Hero, or QuTScloud)
  2. 2. For QTS: Upgrade to version 5.0.0.1986 (build 20220324) or later. For older QTS 4.x branches, note that multiple branches are affected - upgrade to a supported stable branch with fixes
  3. 3. For QuTS Hero: If on h4.x, upgrade to h4.5.4.1771 or later; if on h5.x, upgrade to h5.0.0.1986 (build 20220324) or later
  4. 4. For QuTScloud: Upgrade to version c5.0.1.1998 or later (c5.0.1.1949 and later contains the fix
  5. 5. Perform the upgrade via QNAP Control Panel > Firmware Update or via the cloud console for QuTScloud
  6. 6. After upgrade, verify the firmware version matches or exceeds the fixed build numbers
Caveat Firmware upgrades on QNAP NAS may require restart; ensure backup of critical data before upgrading; some older QTS 4.x branch upgrades may require moving to a newer branch which could have behavior changes

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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