dbcve.org
QtsOperating system · Qnap

CVE-2024-21900

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-08
Fix available
A fix is available. Upgrade to 5.1.3.2578 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated 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 QuTS hero h5.1.3.2578 build 20231110 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

This is a command injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems. The flaw allows authenticated users to execute arbitrary operating system commands through the network interface, likely due to insufficient input validation in a web application component.

MitigationUpgrade affected QNAP devices to the fixed versions (QTS 5.1.3.2578, QuTS hero h5.1.3.2578, or QuTScloud c5.1.5.2651 and later). Prioritize patching internet-facing devices and enforce least-privilege user accounts until upgrade is possible.

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.3.2578= 5.1.3.2578
Quts HeroOperating system
Affected:< h5.1.3.2578= h5.1.3.2578
QutscloudOperating system
Affected:< 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 and version
    Log into the QNAP admin web interface and locate the version information typically found in Control Panel > System > Firmware or in the system dashboard. Alternatively, access the device via SSH and run: cat /etc/config/core_version (QTS/QuTS hero) or cat /etc/version (QuTScloud).
    Affected if The installed version is QTS <= 5.1.3.2578, QuTS hero <= h5.1.3.2578, or QuTScloud < c5.1.5.2651.
  2. Confirm the operating system variant
    In the admin web interface, check the system information page to confirm whether the device runs QTS, QuTS hero, or QuTScloud. Each has distinct version numbering (QTS: plain numbers, QuTS hero: 'h' prefix, QuTScloud: 'c' prefix).
    Affected if The product is QTS, QuTS hero, or QuTScloud and the version falls within the affected ranges listed in step 1.
  3. Verify web application interface is enabled
    Attempt to access the QNAP admin web interface via HTTP/HTTPS on port 8080 or 443 (or configured custom port). Confirm the web service is running by checking if the login page responds.
    Affected if The web interface is accessible and responds, indicating the vulnerable web application component is exposed.
  4. Check authentication status
    Verify that user accounts exist and authentication is enabled on the device. This can be done by attempting to log into the admin interface or via SSH using valid credentials.
    Affected if An authenticated user account can access the system, which is required to exploit this command injection flaw.

A device is affected if it runs QTS <= 5.1.3.2578, QuTS hero <= h5.1.3.2578, or QuTScloud < c5.1.5.2651 and has the web administration interface accessible with valid user accounts.

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.1.3.2578 or later
Fixed in 5.1.3.2578
Interim mitigation

Upgrade affected QNAP devices to the fixed versions (QTS 5.1.3.2578, QuTS hero h5.1.3.2578, or QuTScloud c5.1.5.2651 and later). Prioritize patching internet-facing devices and enforce least-privilege user accounts until upgrade is possible.

Recommended fix High confidence

QTS 5.1.3.2578 (build 20231110 or later); QuTS hero h5.1.3.2578 (build 20231110 or later); QuTScloud c5.1.5.2651 or later

  1. 1. Identify the QNAP product type (QTS, QuTS hero, or QuTScloud) currently running
  2. 2. Check current version by logging into the QNAP admin interface
  3. 3. For QTS users: Upgrade to version 5.1.3.2578 build 20231110 or later
  4. 4. For QuTS hero users: Upgrade to version h5.1.3.2578 build 20231110 or later
  5. 5. For QuTScloud users: Upgrade to version c5.1.5.2651 or later
  6. 6. After upgrade, verify the system is functioning normally and confirm the new version number
Caveat Standard upgrade risks apply - backup critical data before performing system updates

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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