dbcve.org
QtsOperating system · Qnap

CVE-2024-21899

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-08
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 improper authentication vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to compromise the security of the system 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

This is an improper authentication vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems. When exploited over the network, it allows attackers to bypass authentication mechanisms and compromise system security. The vulnerability carries a CRITICAL severity rating due to its network-exploitable nature and potential for complete system compromise.

MitigationOrganizations should immediately identify all affected QNAP devices and update them to the fixed versions (QTS 5.1.3.2578+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, QuTScloud c5.1.5.2651+) to remediate this vulnerability.

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.1.0, < 5.1.3.2578= 4.5.4.2627= 5.1.3.2578
Quts HeroOperating system
Affected:< h4.5.4.2626>= h5.1.0, < h5.1.3.2578= h4.5.4.2626= 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
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 the QNAP product variant
    Log into the QNAP admin web interface and navigate to Control Panel > System > General Settings > About, or run `cat /etc/config/qpkg.xml` via SSH to identify whether the system is running QTS, QuTS hero, or QuTScloud.
    Affected if The system is running QTS, QuTS hero, or QuTScloud and the variant is unknown or unconfirmed.
  2. Check the installed QTS version
    In the web interface, go to Control Panel > System > General Settings > About and note the Build number and Version fields. Alternatively, run `getconf PVER` or `cat /etc/version` via SSH to retrieve the version string.
    Affected if The version is below 4.5.4.2627, or is 5.1.0 through 5.1.3.2578 (inclusive), or exactly 4.5.4.2627 or 5.1.3.2578.
  3. Check the installed QuTS hero version
    In the web interface, navigate to Control Panel > System > General Settings > About and locate the version information. Via SSH, run `cat /etc/version` or `getconf PVER` to retrieve the version string which will contain an 'h' prefix for QuTS hero.
    Affected if The version is below h4.5.4.2626, or is h5.1.0 through h5.1.3.2578 (inclusive), or exactly h4.5.4.2626 or h5.1.3.2578.
  4. Check the installed QuTScloud version
    In the cloud portal or via SSH running `cat /etc/version` or `getconf PVER`, retrieve the version string which will contain a 'c' prefix for QuTScloud.
    Affected if The version is below c5.1.5.2651.
  5. Confirm remote access is enabled
    Verify that the QNAP device has the admin web interface (port 8080 or 443) or SSH (port 22) accessible from the network by checking the device's network settings and firewall rules.
    Affected if The management interface or SSH is exposed to untrusted networks, making remote exploitation possible.

The system is affected if it is running any QTS version < 4.5.4.2627 or between 5.1.0 and 5.1.3.2578, any QuTS hero version < h4.5.4.2626 or between h5.1.0 and h5.1.3.2578, or any QuTScloud version < c5.1.5.2651, and the management interface is network-accessible.

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

Organizations should immediately identify all affected QNAP devices and update them to the fixed versions (QTS 5.1.3.2578+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, QuTScloud c5.1.5.2651+) to remediate this vulnerability.

Recommended fix High confidence

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

  1. 1. Log into the QNAP admin interface
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Check for available updates or manually download the appropriate firmware version
  4. 4. For QTS: upgrade to version 4.5.4.2627 (build 20231225 or later) OR 5.1.3.2578 (build 20231110 or later)
  5. 5. For QuTS hero: upgrade to version h4.5.4.2626 (build 20231225 or later) OR h5.1.3.2578 (build 20231110 or later)
  6. 6. For QuTScloud: upgrade to version c5.1.5.2651 or later
  7. 7. After upgrade, verify the system is functioning normally
Caveat Firmware updates may require system reboot; backup critical data before upgrading

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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