dbcve.org
QtsOperating system · Qnap

CVE-2023-51366

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 path traversal vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to read the contents of unexpected files and expose sensitive data 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

A path traversal vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated users to use directory traversal sequences (e.g., ../) to access files outside the intended web root directory, potentially reading sensitive system files and exposing confidential data over the network.

MitigationApply the vendor-supplied patches by upgrading to QTS 5.1.6.2722 build 20240402 or later, or QuTS hero h5.1.6.2734 build 20240414 or later. Restrict network access to the admin interface until patches are applied.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 admin web interface and navigate to Control Panel > System > About, or via CLI run `getcfg System Version` to determine if the system runs QTS or QuTS hero.
    Affected if The system is identified as either QTS or QuTS hero.
  2. Check the installed QTS version
    In the web interface, go to Control Panel > System > About and note the Build Number and Version. Alternatively, via CLI run `getcfg System Version` and compare the version string to the affected QTS list: 5.1.0.2348 through 5.1.5.2679.
    Affected if The installed QTS 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 installed QuTS hero version
    In the web interface, go to Control Panel > System > About and note the Build Number and Version. Alternatively, via CLI run `getcfg System Version` and compare the version string to the affected QuTS hero list: h5.1.0.2409 through h5.1.5.2680.
    Affected if The installed QuTS hero 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 web administration interface is accessible
    Confirm the QNAP web admin portal (port 8080 or 443) is reachable on the network or locally. This vulnerability is exploitable through the web interface by an authenticated user.
    Affected if The QNAP web admin interface is enabled and network-accessible.

You are affected if your QNAP device runs QTS version 5.1.0.2348 through 5.1.5.2679 or QuTS hero version h5.1.0.2409 through h5.1.5.2680 and the web administration interface is accessible to authenticated users.

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 patches by upgrading to QTS 5.1.6.2722 build 20240402 or later, or QuTS hero h5.1.6.2734 build 20240414 or later. Restrict network access to the admin interface until patches are applied.

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. Identify the current QTS or QuTS hero version by accessing the QNAP admin interface and checking System Settings > About
  2. 2. For QTS systems: Upgrade to QTS version 5.1.6.2722 (build 20240402) or later
  3. 3. For QuTS hero systems: Upgrade to QuTS hero version h5.1.6.2734 (build 20240414) or later
  4. 4. Use the QNAP Control Panel > System > Firmware Update to perform the upgrade
  5. 5. After upgrade, verify the new version by checking System Settings > About to confirm the version number matches or exceeds the fixed release

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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