dbcve.org
QtsOperating system · Qnap

CVE-2023-50364

HIGH · 8.8 CVSS v3.1 Published 2024-04-26
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
A buffer copy without checking size of input vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated users to execute code 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

A buffer copy without checking size vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated users to execute arbitrary code via network. The flaw stems from missing size bounds checking during buffer operations, enabling a buffer overflow that can be exploited for remote code execution.

MitigationUpgrade QNAP devices to QTS 5.1.6.2722 build 20240402 or later / QuTS hero h5.1.6.2734 build 20240414 or later. Until patched, restrict administrative access to trusted users only and minimize network exposure.

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 the QNAP operating system type
    Log into the QNAP device admin console and check the System Information or use the command line to determine if the system is running QTS or QuTS hero
    Affected if The system is running QTS or QuTS hero (the vulnerability only affects these operating systems)
  2. Check the QTS build version
    In the admin console, go to Control Panel > System > System Information > General, or run the command 'getsysinfo' or 'version' via SSH to retrieve the exact build version
    Affected if The QTS build version matches any of these: 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. Check the QuTS hero build version
    In the admin console, go to Control Panel > System > System Information > General, or run the command 'getsysinfo' or 'version' via SSH to retrieve the exact build version. Note that QuTS hero versions are prefixed with 'h'
    Affected if The QuTS hero build version matches any of these: 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. Verify network exposure of admin interface
    Check if the QNAP admin web interface (ports 8080, 443) or SSH (port 22) is accessible from untrusted networks by reviewing firewall rules or router port forwarding settings
    Affected if The administrative interface is exposed to the internet or untrusted networks, increasing exploitation risk

A system is affected if it runs QTS or QuTS hero and its exact build version matches any of the versions listed in the affected versions list for that operating system.

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

Upgrade QNAP devices to QTS 5.1.6.2722 build 20240402 or later / QuTS hero h5.1.6.2734 build 20240414 or later. Until patched, restrict administrative access to trusted users only and minimize network exposure.

Recommended fix High confidence

QTS 5.1.6.2722 (build 20240402) or later for QTS; QuTS hero h5.1.6.2734 (build 20240414) or later for QuTS Hero

  1. 1. Identify whether the device is running QTS or QuTS Hero operating system
  2. 2. Check the current firmware version in System Settings > Storage & Snapshots > Overview (or similar)
  3. 3. If running QTS version 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, or 5.1.0.2444, upgrade to QTS 5.1.6.2722 build 20240402 or later
  4. 4. If running QuTS Hero version h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, or h5.1.0.2466, upgrade to QuTS hero h5.1.6.2734 build 20240414 or later
  5. 5. Download the firmware from the official QNAP download center and apply via System Settings > Firmware Update
  6. 6. Verify the upgrade was successful and the new version is running
Caveat Standard QNAP firmware upgrade - ensure backups are current and review release notes for any configuration considerations

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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