dbcve.org
QtsOperating system · Qnap

CVE-2024-21898

HIGH · 8.8 CVSS v3.1 Published 2024-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An OS command 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.6.2722 build 20240402 and later QuTS hero h5.1.6.2734 build 20240414 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

OS command injection vulnerability in QNAP QTS and QuTS hero NAS operating systems allowing authenticated users to execute arbitrary commands via network. The vulnerability has high CVSS (8.8) indicating significant impact if exploited.

MitigationUpdate QTS to version 5.1.6.2722 build 20240402 or later, or QuTS hero to version h5.1.6.2734 build 20240414 or later. Ensure authentication controls are reviewed since valid credentials are required for exploitation.

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
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

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 your QNAP NAS model and OS type
    Log into the QNAP web interface and check the System Dashboard, or run 'cat /etc/config/defunct_info' via SSH to see if the device runs QTS or QuTS hero
    Affected if The device is a QNAP NAS running QTS or QuTS hero
  2. Determine the installed QTS version
    In the QNAP web UI, go to Control Panel > System > Firmware Update > Firmware Information, or run 'getconf PVER' via SSH to retrieve the firmware version
    Affected if The version matches any of: 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, or 5.1.5.2679
  3. Determine the installed QuTS hero version
    In the QNAP web UI, go to Control Panel > System > Firmware Update > Firmware Information, or run 'getconf PVER' via SSH to retrieve the firmware version
    Affected if The version matches any of: 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, or h5.1.5.2680
  4. Confirm remote management interface accessibility
    Attempt to access the QNAP web interface from an external network, or check the router NAT/port forwarding rules for port 8080 or 443 pointing to the NAS
    Affected if The QTS/QuTS hero admin interface is reachable from the network and the device version is in the affected list
  5. Verify authentication is enabled and in use
    Check that local user accounts or domain authentication is configured in Control Panel > Privilege > Users, and confirm that anonymous access is disabled
    Affected if User accounts exist on the system and the device version is in the affected list (valid credentials are required for exploitation)

A user is affected if their QNAP NAS runs QTS or QuTS hero with a version matching any of the listed affected versions and the admin interface is network-accessible with valid user accounts configured.

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

Update QTS to version 5.1.6.2722 build 20240402 or later, or QuTS hero to version h5.1.6.2734 build 20240414 or later. Ensure authentication controls are reviewed since valid credentials are required for exploitation.

Recommended fix High confidence

QTS 5.1.6.2722 build 20240402 or later; QuTS hero h5.1.6.2734 build 20240414 or later

  1. 1. Log into the QNAP admin interface and navigate to Control Panel > System > Firmware Update to identify your current QTS or QuTS hero version
  2. 2. Confirm your current version matches one of the affected versions: QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, or 5.1.0.2444; QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, or h5.1.0.2466
  3. 3. Back up all critical data on the NAS as a precaution before applying any firmware update
  4. 4. Download the firmware update from the official QNAP download center at https://download.qnap.com
  5. 5. For QTS systems: Update to QTS 5.1.6.2722 build 20240402 or later
  6. 6. For QuTS hero systems: Update to QuTS hero h5.1.6.2734 build 20240414 or later
  7. 7. Verify the update was successful by checking the firmware version in Control Panel > System > Firmware Update after reboot
Caveat QNAP firmware updates carry standard risks including potential temporary service interruption; ensure backups are verified before proceeding

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

Fix this in Qts 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 help mitigating

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-21898 — 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-21898 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