dbcve.org
QtsOperating system · Qnap

CVE-2023-51367

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
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 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 · moderate confidence

Buffer overflow vulnerability in QNAP NAS operating systems where a copy operation does not validate input size, potentially allowing remote code execution via network. The flaw stems from insufficient bounds checking during data handling.

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. Prior to updating, schedule maintenance window and backup critical data.

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 OS type
    Log into the QNAP device Control Panel or System Administration. Look for the operating system name displayed on the dashboard - it will be either QTS or QuTS Hero.
    Affected if The device is running QTS or QuTS Hero (other QNAP OS variants are not affected by this specific CVE)
  2. Find the installed QTS version and build number
    In QTS, go to Control Panel > System > Firmware Update. The version and build number are displayed on the System Dashboard or in Control Panel > System > About (for example: 5.1.5.2679).
    Affected if The installed QTS version matches any of these 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, or 5.1.5.2679
  3. Find the installed QuTS Hero version and build number
    In QuTS Hero, go to Control Panel > System > Firmware Update. The version and build number appear on the System Dashboard or in Control Panel > System > About (for example: h5.1.5.2680).
    Affected if The installed QuTS Hero version matches any of these builds: 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 the firmware is below the patched builds
    Compare your installed build number to the fixed versions: QTS build 5.1.6.2722 or QuTS Hero build h5.1.6.2734. If your current build is lower than these, the vulnerability is present.
    Affected if The installed build is earlier than QTS 5.1.6.2722 or QuTS Hero h5.1.6.2734

A device is affected if it runs QTS or QuTS Hero and the installed build number matches one of the specific versions listed in the affected products list.

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. Prior to updating, schedule maintenance window and backup critical data.

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 (QTS or QuTS hero)
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Check the current firmware version under System Information to confirm it matches one of the affected versions
  4. 4. Use the firmware update feature to check for and install the latest available update
  5. 5. Ensure the installed version is QTS 5.1.6.2722 build 20240402 or later, or QuTS hero h5.1.6.2734 build 20240414 or later
  6. 6. After update completion, verify the firmware version has been successfully upgraded

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-2023-51367 — 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-51367 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