dbcve.org
QtsOperating system · Qnap

CVE-2023-34972

MEDIUM · 6.5 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 →
70/100
Remediation priority · Elevated
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 cleartext transmission of sensitive information vulnerability has been reported to affect QNAP operating systems. If exploited, the vulnerability possibly allows local network clients to read the contents of unexpected sensitive data 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 a cleartext transmission vulnerability in QNAP NAS operating systems where sensitive data is transmitted over the network without encryption. Local attackers on the same network can intercept and read sensitive information due to the lack of encryption in data transmission.

MitigationUpdate QNAP firmware to the fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, or QuTS hero h5.1.0.2424+) to remediate. Prioritize systems with sensitive data accessible over local networks.

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

CVSS:3.1/AV:A/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. Check QTS firmware version
    Log into the QNAP admin interface and navigate to Control Panel > System > Firmware Update, or run the command `qmgr -g` via SSH to retrieve the installed QTS version.
    Affected if The version displayed is >= 5.0.1 but < 5.0.1.2425, or >= 5.1.0 but < 5.1.0.2444
  2. Check QuTS Hero firmware version
    If the device runs QuTS Hero instead of QTS, log into the admin interface and navigate to Control Panel > System > Firmware Update, or run `qmgr -g` via SSH to retrieve the installed QuTS Hero version.
    Affected if The version displayed is >= h5.1.0 but < h5.1.0.2424
  3. Verify network exposure of NAS services
    Review network configuration in Control Panel > Network & Virtual Switch to determine if sensitive NAS services (file sharing, management interface) are accessible over the local network without VPN or encryption.
    Affected if Sensitive services are exposed to the local network where an attacker could intercept cleartext traffic
  4. Confirm affected version against CVE ranges
    Compare the exact numeric version obtained from step 1 or 2 against the vulnerable ranges: QTS 5.0.1.x < 2425, QTS 5.1.0.x < 2444, or QuTS Hero h5.1.0.x < 2424.
    Affected if The installed version number falls within any of the listed vulnerable version ranges

The system is affected if the installed QTS or QuTS Hero version matches the vulnerable ranges and sensitive data is accessible over the network.

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

Update QNAP firmware to the fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, or QuTS hero h5.1.0.2424+) to remediate. Prioritize systems with sensitive data accessible over local networks.

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 accessing the QNAP admin interface and navigating to Control Panel > System > Firmware Update, or via the command line using `getsysinfo` or `cat /etc/version`
  2. 2. Compare the current version against the affected version ranges: QTS 5.0.1 to 5.0.1.2424, QTS 5.1.0 to 5.1.0.2443, or QuTS hero h5.1.0 to h5.1.0.2423
  3. 3. If the current version is within an affected range, download the appropriate fixed version from QNAP's support website: QTS 5.0.1.2425 (build 20230609) or later, QTS 5.1.0.2444 (build 20230629) or later, or QuTS hero h5.1.0.2424 (build 20230609) or later
  4. 4. Back up critical data on the NAS before performing the firmware upgrade
  5. 5. Apply the firmware update via Control Panel > System > Firmware Update > Check for Update, or manually upload the firmware file if using offline update
  6. 6. After upgrade, verify the system is running a fixed version (5.0.1.2425+, 5.1.0.2444+, or h5.1.0.2424+)
Caveat Standard QNAP firmware update risks apply - ensure critical data is backed up before upgrading; some configuration changes may be reset to defaults

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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