dbcve.org
QtsOperating system · Qnap

CVE-2023-51365

HIGH · 7.5 CVSS v3.1 Published 2024-04-26
Fix available
A fix is available. Upgrade to 4.5.4.2627 / 5.1.4.2596 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.4.2596 build 20231128 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.3.2578 build 20231110 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 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

This is a path traversal vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems. The flaw allows authenticated or unauthenticated remote attackers to escape the intended directory boundaries using directory traversal sequences (e.g., ../) in requests, enabling unauthorized access to read sensitive files outside the web root.

MitigationUpdate affected QNAP systems to the fixed versions (QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, QuTScloud c5.1.5.2651+). If patching is delayed, restrict network access to the management interfaces and implement WAF rules to block traversal patterns.

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:>= 4.5.1, < 4.5.4.2627>= 5.1.0, < 5.1.4.2596= 4.5.4.2627= 5.1.4.2596
Quts HeroOperating system
Affected:>= h4.5.0, < h4.5.4.2626>= h5.1.0, < h5.1.3.2578= h4.5.4.2626= h5.1.3.2578
QutscloudOperating system
Affected:>= c5.0.0.1919, < c5.1.5.2651

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

CVSS:3.1/AV:N/AC:L/PR:N/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 product type
    Log into the QNAP admin interface and check System Information > Overview, or run `getsysinfo` via SSH to determine if the system runs QTS, QuTS hero, or QuTScloud
    Affected if The system is any of these three product types and the version falls within the affected ranges
  2. Determine the installed QTS version
    In the web UI, go to Control Panel > System > System Information > System Status. Or via SSH, check `cat /etc/config/.qts_version` or use the `vers` command
    Affected if The version is QTS 4.5.1 through 4.5.4.2627 (excluding 4.5.4.2627), or QTS 5.1.0 through 5.1.4.2596 (excluding 5.1.4.2596)
  3. Determine the installed QuTS hero version
    In the web UI, go to Control Panel > System > System Information > System Status. Or via SSH, check `cat /etc/config/.quts_version` or use the `vers` command
    Affected if The version is QuTS hero h4.5.0 through h4.5.4.2626 (excluding h4.5.4.2626), or QuTS hero h5.1.0 through h5.1.3.2578 (excluding h5.1.3.2578)
  4. Determine the installed QuTScloud version
    Check the cloud console or the local admin interface for the QuTScloud version number
    Affected if The version is QuTScloud c5.0.0.1919 through c5.1.5.2651 (excluding c5.1.5.2651)
  5. Verify web management interface is accessible
    Confirm the QNAP web server (typically port 8080 or 443) is running and reachable. Check via `http://<your-nas-ip>:<port>` in a browser or via `curl -k https://<your-nas-ip>`
    Affected if The web interface is exposed and the version falls within any of the affected ranges listed above

A system is affected if it runs QTS, QuTS hero, or QuTScloud with a version number within the affected ranges AND the web management interface is accessible.

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
Upgrade available Upgrade to 4.5.4.2627 / 5.1.4.2596 or later
Fixed in 4.5.4.26275.1.4.2596
Interim mitigation

Update affected QNAP systems to the fixed versions (QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, QuTScloud c5.1.5.2651+). If patching is delayed, restrict network access to the management interfaces and implement WAF rules to block traversal patterns.

Recommended fix High confidence

QTS 4.5.4.2627 (build 20231225+), QTS 5.1.4.2596 (build 20231128+), QuTS hero h4.5.4.2626 (build 20231225+), QuTS hero h5.1.3.2578 (build 20231110+), or QuTScloud c5.1.5.2651+ depending on product line

  1. 1. Identify your current QNAP product and version (QTS, QuTS hero, or QuTScloud) by accessing the QNAP admin interface and checking System Administration > Firmware Version
  2. 2. Determine if your current version is affected by comparing against the vulnerable version ranges: QTS >= 4.5.1 but < 4.5.4.2627 or < 5.1.4.2596; QuTS hero >= h4.5.0 but < h4.5.4.2626 or >= h5.1.0 but < h5.1.3.2578; QuTScloud >= c5.0.0.1919 but < c5.1.5.2651
  3. 3. Back up all critical data and configurations before performing any firmware upgrade
  4. 4. Access the QNAP admin interface and navigate to Control Panel > System Administration > Firmware Update
  5. 5. Select the appropriate fixed version for your product: For QTS 4.x, upgrade to version 4.5.4.2627 (build 20231225 or later); For QTS 5.x, upgrade to version 5.1.4.2596 (build 20231128 or later); For QuTS hero h4.x, upgrade to version h4.5.4.2626 (build 20231225 or later); For QuTS hero h5.x, upgrade to version h5.1.3.2578 (build 20231110 or later); For QuTScloud, upgrade to version c5.1.5.2651
  6. 6. Complete the firmware update and verify the new version is installed correctly
Caveat Review QNAP release notes for your specific version upgrade to check for any configuration or feature changes that may impact your deployment

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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