dbcve.org
QtsOperating system · Qnap

CVE-2023-34973

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-24
Fix available
A fix is available. Upgrade to 5.0.1.2425 / 5.1.0.2444 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An insufficient entropy vulnerability has been reported to affect QNAP operating systems. If exploited, the vulnerability possibly allows remote users to predict secret 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 QuTS hero h5.1.0.2424 build 20230609 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 an insufficient entropy vulnerability in QNAP operating systems where the random number generation lacks sufficient entropy, potentially allowing remote users to predict secret values through unspecified vectors.

MitigationUpgrade QNAP devices to QTS 5.0.1.2425 (build 20230609), QTS 5.1.0.2444 (build 20230629), or QuTS hero h5.1.0.2424 (build 20230609) or later to resolve the insufficient entropy issue.

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.0.1, < 5.0.1.2425>= 5.1.0, < 5.1.0.2444
Quts HeroOperating system
Affected:>= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 QTS firmware version
    Access the QNAP admin console, go to Control Panel > System > Firmware Update, or run the command 'getcfg system version' via SSH/CLI to retrieve the installed firmware version and build number
    Affected if The version displayed is 5.0.1.x where x is less than 2425, or 5.1.0.x where x is less than 2444
  2. Identify QuTS Hero firmware version
    Access the QNAP admin console for QuTS Hero devices, navigate to Control Panel > System > Firmware Update, or run the command 'getcfg system version' via SSH/CLI to retrieve the installed firmware version and build number
    Affected if The version displayed is h5.1.0.x where x is less than 2424
  3. Confirm device is a QNAP NAS
    Verify the device is a QNAP Network Attached Storage (NAS) running QTS or QuTS Hero operating system by checking the dashboard or system information page in the admin console
    Affected if The device is not a QNAP NAS or is running a different operating system (the vulnerability applies only to QNAP QTS and QuTS Hero)
  4. Determine if random number generation is in use
    Review system logs or consult with application administrators to identify if the NAS is generating cryptographic secrets (keys, tokens, session IDs, passwords) that rely on the system's random number generator
    Affected if The system generates or uses cryptographic secrets - the vulnerability affects any application relying on the OS random number generator for secret values

The user is affected if the QNAP device runs QTS versions 5.0.1 through 5.0.1.2424 or 5.1.0 through 5.1.0.2443, or QuTS Hero h5.1.0 through h5.1.0.2423, and the system uses random number generation for cryptographic purposes.

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.0.1.2425 / 5.1.0.2444 or later
Fixed in 5.0.1.24255.1.0.2444
Interim mitigation

Upgrade QNAP devices to QTS 5.0.1.2425 (build 20230609), QTS 5.1.0.2444 (build 20230629), or QuTS hero h5.1.0.2424 (build 20230609) or later to resolve the insufficient entropy issue.

Recommended fix High confidence

QTS 5.0.1.2425 (build 20230609), QTS 5.1.0.2444 (build 20230629), or QuTS hero h5.1.0.2424 (build 20230609) depending on current branch

  1. 1. Identify the current QTS or QuTS hero version by navigating to Control Panel > System > Firmware Update
  2. 2. If running QTS 5.0.x, upgrade to QTS 5.0.1.2425 build 20230609 or later
  3. 3. If running QTS 5.1.x, upgrade to QTS 5.1.0.2444 build 20230629 or later
  4. 4. If running QuTS hero h5.1.x, upgrade to QuTS hero h5.1.0.2424 build 20230609 or later
  5. 5. After upgrade, verify the build number matches or exceeds the fixed version for your branch
Caveat Review QNAP release notes for your target version to check for any configuration changes or feature modifications before upgrading

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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