dbcve.org
QtsOperating system · Qnap

CVE-2023-32974

HIGH · 7.5 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 5.1.0.2444 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.0.2444 build 20230629 and later QuTS hero h5.1.0.2424 build 20230609 and later QuTScloud c5.1.0.2498 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, QuTS hero, and QuTScloud operating systems allows attackers to use directory traversal sequences (e.g., '../') to access files outside the intended web root directory. This enables unauthorized reading of sensitive system files, configurations, and user data that should not be publicly accessible.

MitigationUpdate affected QNAP devices to the fixed versions: QTS 5.1.0.2444 build 20230629 or later, QuTS hero h5.1.0.2424 build 20230609 or later, or QuTScloud c5.1.0.2498 or later. Restrict network access to administrative interfaces as an interim control until patching is complete.

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, < 5.1.0.2444
Quts HeroOperating system
Affected:>= h5.1.0, < h5.1.0.2424
QutscloudOperating system
Affected:>= c5.0.0.1919, < c5.1.0.2498

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 and firmware version
    Log into the QNAP device via SSH or the web interface. In the web UI, go to Control Panel > System > Firmware Update > Firmware Information to see the exact version and build number. Alternatively, run 'cat /etc/config/version' via SSH.
    Affected if The product is QTS, QuTS hero, or QuTScloud AND the version falls within the affected ranges (QTS < 5.1.0.2444, QuTS hero < h5.1.0.2424, QuTScloud < c5.1.0.2498)
  2. Verify the web server is enabled
    Confirm that the QNAP web management interface (typically ports 8080 or 443) is accessible and running. This is required because the path traversal vulnerability exists in the web server component.
    Affected if The web interface is exposed and the firmware version is within the affected range
  3. Check for unauthorized access attempts
    Review web server access logs for unusual path traversal patterns. On QNAP devices, check /var/log/httpd-access.log or the logs accessible via Log Center in the web UI. Look for sequences like '../', '..%2F', or URL-encoded traversal patterns.
    Affected if Logs show repeated traversal attempts accessing paths outside the web root (e.g., /etc/passwd, /share)

A user is affected if they are running QTS < 5.1.0.2444, QuTS hero < h5.1.0.2424, or QuTScloud < c5.1.0.2498 AND the web management interface is accessible, allowing unauthenticated path traversal to read sensitive files outside the web root.

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 5.1.0.2444 or later
Fixed in 5.1.0.2444
Interim mitigation

Update affected QNAP devices to the fixed versions: QTS 5.1.0.2444 build 20230629 or later, QuTS hero h5.1.0.2424 build 20230609 or later, or QuTScloud c5.1.0.2498 or later. Restrict network access to administrative interfaces as an interim control until patching is complete.

Recommended fix High confidence

QTS 5.1.0.2444 / QuTS hero h5.1.0.2424 / QuTScloud c5.1.0.2498

  1. 1. Identify the QNAP product type running (QTS, QuTS hero, or QuTScloud)
  2. 2. Check the current version of the installed QNAP operating system
  3. 3. For QTS: Upgrade to version 5.1.0.2444 (build 20230629) or later
  4. 4. For QuTS hero: Upgrade to version h5.1.0.2424 (build 20230609) or later
  5. 5. For QuTScloud: Upgrade to version c5.1.0.2498 or later
  6. 6. After upgrade, verify the new version is applied and the vulnerability is resolved

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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