dbcve.org
QtsOperating system · Qnap

CVE-2024-50400

HIGH · 7.2 CVSS v3.1 Published 2024-11-22
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.1.2930 build 20241025 and later QuTS hero h5.2.1.2929 build 20241025 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 is passed as a format string to sensitive functions. When exploited by attackers who already have administrator access, it allows reading sensitive data from memory or modifying memory contents, potentially exposing secrets or altering system state.

MitigationApply the vendor-supplied firmware updates (QTS 5.2.1.2930 build 20241025 or QuTS hero h5.2.1.2929 build 20241025 and later) to all affected devices. Since the vulnerability requires administrator-level access, ensure strong administrator credentials and monitor for credential compromise as a primary defense layer.

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.2.0.2737= 5.2.0.2744= 5.2.0.2782= 5.2.0.2802= 5.2.0.2823= 5.2.0.2851= 5.2.0.2860
Quts HeroOperating system
Affected:= h5.2.0.2737= h5.2.0.2782= h5.2.0.2789= h5.2.0.2802= h5.2.0.2823= h5.2.0.2851= h5.2.0.2860

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 QNAP OS type
    Log into the QNAP device admin console and check the operating system. Look for either QTS or QuTS hero in the system information or dashboard.
    Affected if The device is running QTS or QuTS hero operating system
  2. Check QTS firmware version
    In QTS admin panel, go to Control Panel > System > Firmware Update > Check for Updates, or navigate to Control Panel > System > About. Record the Build Number and Firmware Version shown.
    Affected if The version matches any of: 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, 5.2.0.2802, 5.2.0.2823, 5.2.0.2851, or 5.2.0.2860
  3. Check QuTS hero firmware version
    In QuTS hero admin panel, go to Control Panel > System > Firmware Update > Check for Updates, or navigate to Control Panel > System > About. Record the Build Number and Firmware Version shown.
    Affected if The version matches any of: h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802, h5.2.0.2823, h5.2.0.2851, or h5.2.0.2860
  4. Verify administrator access status
    Review user accounts in Control Panel > Privilege > Users. Confirm that only trusted administrators exist and that strong, unique passwords are in use.
    Affected if Weak or compromised administrator credentials are present, since this vulnerability requires administrator-level access to exploit

The device is affected if it runs QTS or QuTS hero with any of the listed firmware versions and the attacker already has administrator credentials.

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

Apply the vendor-supplied firmware updates (QTS 5.2.1.2930 build 20241025 or QuTS hero h5.2.1.2929 build 20241025 and later) to all affected devices. Since the vulnerability requires administrator-level access, ensure strong administrator credentials and monitor for credential compromise as a primary defense layer.

Recommended fix High confidence

QTS 5.2.1.2930 (build 20241025) or QuTS hero h5.2.1.2929 (build 20241025), depending on product

  1. 1. Identify whether the device runs QTS or QuTS hero operating system
  2. 2. Check the current firmware version in the QNAP admin interface (Control Panel > System > Firmware Update)
  3. 3. If running QTS version 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802, upgrade to QTS 5.2.1.2930 build 20241025 or later
  4. 4. If running QuTS hero version h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802, upgrade to QuTS hero h5.2.1.2929 build 20241025 or later
  5. 5. After upgrade, verify the new firmware version matches or exceeds the fixed releases
Caveat Standard QNAP firmware upgrade risks apply - ensure backups are current and power is stable during update

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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