dbcve.org
QtsOperating system · Qnap

CVE-2023-34971

HIGH · 8.8 CVSS v3.1 Published 2023-08-24
Fix available
A fix is available. Upgrade to 4.5.4.2467 / 5.0.1.2425 or later.
See remediation →
93/100
Remediation priority · Urgent
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
An inadequate encryption strength vulnerability has been reported to affect QNAP operating systems. If exploited, the vulnerability possibly allows local network clients to decrypt the data using brute force attacks via unspecified vectors. We have already fixed the vulnerability in the following versions: QTS 5.0.1.2425 build 20230609 and later QTS 5.1.0.2444 build 20230629 and later QTS 4.5.4.2467 build 20230718 and later QuTS hero h5.1.0.2424 build 20230609 and later QuTS hero h4.5.4.2476 build 20230728 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

QNAP devices running QTS and QuTS hero operating systems use inadequate encryption strength, allowing authenticated local network clients to decrypt sensitive data through brute force attacks. The vulnerability stems from weak cryptographic algorithms or insufficient key lengths in the system's encryption implementation.

MitigationOrganizations should immediately identify affected QNAP devices on their network and upgrade to the fixed QTS or QuTS hero versions (QTS 5.0.1.2425+, 5.1.0.2444+, 4.5.4.2467+ or QuTS hero h5.1.0.2424+, h4.5.4.2476+) following vendor upgrade procedures and testing protocols.

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.4, < 4.5.4.2467>= 5.0.1, < 5.0.1.2425>= 5.1.0, < 5.1.0.2444
Quts HeroOperating system
Affected:>= h4.5.4, < h4.5.4.2476>= h5.1.0, < h5.1.0.2424

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

CVSS:3.1/AV:A/AC:L/PR:N/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. Confirm QNAP device and OS type
    Access the QNAP device's web administration console (usually via https://[device-ip]) and navigate to Control Panel > System > System Information, or use the CLI command `get_sysinfo` via SSH to identify if the device runs QTS or QuTS hero.
    Affected if The device is not a QNAP device or does not run QTS or QuTS hero.
  2. Identify installed QTS version
    In the web console, check the 'Firmware Version' field under System Information. Alternatively, run `cat /etc/config/def_etc_issue` or check the output of `sysctl kern.osrevision` to determine the exact QTS version number.
    Affected if QTS version is 4.5.4.x where x < 2467, OR 5.0.1.x where x < 2425, OR 5.1.0.x where x < 2444.
  3. Identify installed QuTS hero version
    In the web console, check the 'Firmware Version' field under System Information. The version will be prefixed with 'h' (e.g., h4.5.4.x or h5.1.0.x).
    Affected if QuTS hero version is h4.5.4.x where x < 2476, OR h5.1.0.x where x < 2424.
  4. Verify device is accessible on local network
    Confirm the QNAP device has a local network IP address and network services (SMB, AFP, NFS, or QNAP-specific services) are enabled and accessible to authenticated users on the same network segment.
    Affected if The device is exposed on the local network and allows authenticated clients to access file services or the admin interface.

The environment is affected if a QNAP device runs QTS versions 4.5.4.x (<2467), 5.0.1.x (<2425), or 5.1.0.x (<2444); or QuTS hero versions h4.5.4.x (<2476) or h5.1.0.x (<2424), and the device is accessible to authenticated local network 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
Upgrade available Upgrade to 4.5.4.2467 / 5.0.1.2425 / 5.1.0.2444 or later
Fixed in 4.5.4.24675.0.1.24255.1.0.2444
Interim mitigation

Organizations should immediately identify affected QNAP devices on their network and upgrade to the fixed QTS or QuTS hero versions (QTS 5.0.1.2425+, 5.1.0.2444+, 4.5.4.2467+ or QuTS hero h5.1.0.2424+, h4.5.4.2476+) following vendor upgrade procedures and testing protocols.

Recommended fix High confidence

Upgrade to the fixed version matching your current branch: QTS 4.5.4.2467+, QTS 5.0.1.2425+, QTS 5.1.0.2444+, QuTS hero h4.5.4.2476+, or QuTS hero h5.1.0.2424+

  1. 1. Identify the current QNAP firmware version (QTS or QuTS hero) via the QNAP Control Panel > System > Firmware Update
  2. 2. Determine which firmware branch is currently installed: QTS 4.5.4.x, QTS 5.0.1.x, QTS 5.1.0.x, QuTS hero h4.5.4.x, or QuTS hero h5.1.0.x
  3. 3. For QTS 4.5.4.x systems: upgrade to QTS version 4.5.4.2467 (build 20230718) or later
  4. 4. For QTS 5.0.1.x systems: upgrade to QTS version 5.0.1.2425 (build 20230609) or later
  5. 5. For QTS 5.1.0.x systems: upgrade to QTS version 5.1.0.2444 (build 20230629) or later
  6. 6. For QuTS hero h4.5.4.x systems: upgrade to QuTS hero version h4.5.4.2476 (build 20230728) or later
  7. 7. For QuTS hero h5.1.0.x systems: upgrade to QuTS hero version h5.1.0.2424 (build 20230609) or later
  8. 8. After upgrade, verify the firmware version has been successfully updated via Control Panel > System > Firmware Update
Caveat Review QNAP release notes for your specific version upgrade to check for any breaking changes or required migration steps before proceeding

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-34971 — 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-34971 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