dbcve.org
QtsOperating system · Qnap

CVE-2023-51364

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

A path traversal vulnerability in QNAP operating systems (QTS, QuTS hero, QuTScloud) allows authenticated or unauthenticated attackers to access files outside the intended directory by manipulating file path inputs. This exposes sensitive system data across the network.

MitigationApply the appropriate firmware update for the specific QNAP OS version (QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) to remediate the vulnerability.

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 QNAP product type
    Log into the QNAP admin interface and check the System Information page to determine if the system is running QTS, QuTS hero, or QuTScloud
    Affected if The product is QTS, QuTS hero, or QuTScloud and the version falls within the affected ranges
  2. Check QTS version
    In the QTS admin panel, navigate to Control Panel > System > Firmware Update > System Information to view the current QTS version number
    Affected if Version is >= 4.5.1 and < 4.5.4.2627, OR >= 5.1.0 and < 5.1.4.2596, OR equals exactly 4.5.4.2627 or 5.1.4.2596
  3. Check QuTS hero version
    In the QuTS hero admin panel, navigate to Control Panel > System > Firmware Update > System Information to view the current QuTS hero version number
    Affected if Version is >= h4.5.0 and < h4.5.4.2626, OR >= h5.1.0 and < h5.1.3.2578, OR equals exactly h4.5.4.2626 or h5.1.3.2578
  4. Check QuTScloud version
    Access the QuTScloud System Information page through the cloud management console or SSH access to view the current QuTScloud version number
    Affected if Version is >= c5.0.0.1919 and < c5.1.5.2651
  5. Verify web management interface exposure
    Confirm whether the QNAP web administration interface (ports 8080 or 443) is accessible from the network or internet
    Affected if The web interface is network-accessible and the QNAP OS version is within the affected ranges listed above

A system is affected if it is running QTS versions 4.5.1 through 4.5.4.2626, 5.1.0 through 5.1.4.2595, QuTS hero h4.5.0 through h4.5.4.2625, h5.1.0 through h5.1.3.2577, or QuTScloud c5.0.0.1919 through c5.1.5.2650, with the web management interface network-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

Apply the appropriate firmware update for the specific QNAP OS version (QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) to remediate the vulnerability.

Recommended fix High confidence

QTS 4.5.4.2627 (build 20231225+) or QTS 5.1.4.2596 (build 20231128+); QuTS hero h4.5.4.2626 (build 20231225+) or h5.1.3.2578 (build 20231110+); QuTScloud c5.1.5.2651+

  1. Identify the current QNAP firmware version (QTS, QuTS hero, or QuTScloud) via the QNAP Control Panel > System Settings > Firm Update
  2. Navigate to the App Center and ensure all applications are updated before proceeding
  3. Access QNAP Control Panel > System Settings > Firmware Update
  4. Select 'Check for Update' to identify available updates
  5. For QTS systems: Upgrade to QTS 4.5.4.2627 build 20231225 or later, OR QTS 5.1.4.2596 build 20231128 or later
  6. For QuTS hero systems: Upgrade to QuTS hero h4.5.4.2626 build 20231225 or later, OR QuTS hero h5.1.3.2578 build 20231110 or later
  7. For QuTScloud systems: Upgrade to QuTScloud c5.1.5.2651 or later
  8. After upgrade, verify the new firmware version matches the fixed versions listed
Caveat Review QNAP release notes for your specific model before upgrading; major version jumps (e.g., 4.5.x to 5.x) may introduce UI or feature changes

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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