dbcve.org
QtsOperating system · Qnap

CVE-2024-50403

HIGH · 7.2 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 use of externally-controlled format string vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained administrator access to obtain secret data or modify memory. We have already fixed the vulnerability in the following versions: QTS 5.2.2.2950 build 20241114 and later QuTS hero h5.2.2.2952 build 20241116 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

This is a format string vulnerability in QNAP QTS and QuTS hero operating systems where externally-controlled input (from an authenticated administrator session) is used as a format string parameter. This can be exploited to read arbitrary memory contents (potentially exposing secrets like API keys, passwords, or session tokens) or write to memory locations to modify program behavior.

MitigationUpdate affected QNAP devices to QTS 5.2.2.2950 build 20241114 or later, or QuTS hero h5.2.2.2952 build 20241116 or later. Since the vulnerability requires administrator access, ensure admin accounts use strong, unique credentials and enable multi-factor authentication.

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= 5.1.6.2722
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= h5.1.6.2734= h5.1.7.2770

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

CVSS:3.1/AV:N/AC:L/PR:H/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 QTS or QuTS hero version
    Log into the QNAP device admin console, go to Control Panel > System > Firmware Update, or use the command 'getsysinfo' via SSH to retrieve the firmware build version
    Affected if The displayed build version matches any of these QTS builds: 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, 5.1.6.2722 OR these QuTS hero builds: h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1
  2. Confirm the product type
    Verify whether the device runs QTS or QuTS hero - this is visible in the admin dashboard footer or via 'getsysinfo' output under the OS name field
    Affected if The device runs either QTS or QuTS hero and the version matches the affected builds listed above
  3. Verify administrator access exists
    The vulnerability requires an authenticated administrator session. Check if there are any admin accounts configured and whether remote administrator access is enabled via Control Panel > Security
    Affected if An attacker with administrator credentials could exploit this flaw; check if weak or compromised admin passwords exist or if MFA is disabled in Control Panel > Security > Account

You are affected if your QNAP device runs QTS or QuTS hero with any of the specific build versions listed above, and an attacker could obtain administrator-level access.

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 affected QNAP devices to QTS 5.2.2.2950 build 20241114 or later, or QuTS hero h5.2.2.2952 build 20241116 or later. Since the vulnerability requires administrator access, ensure admin accounts use strong, unique credentials and enable multi-factor authentication.

Recommended fix High confidence

QTS 5.2.2.2950 (build 20241114) or later / QuTS hero h5.2.2.2952 (build 20241116) or later

  1. 1. Log in to the QNAP admin console as administrator
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Click 'Check for Update' to see if the new version is available
  4. 4. If available, click 'Update Now' to install QTS 5.2.2.2950 (build 20241114) or later for QTS systems, or QuTS hero h5.2.2.2952 (build 20241116) or later for QuTS hero systems
  5. 5. Wait for the update to complete and for the system to reboot
  6. 6. Verify the update was successful by checking Control Panel > System > Firmware Update > Version Info
Caveat QNAP firmware updates may temporarily interrupt services; ensure backups are current 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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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