dbcve.org
QtsOperating system · Qnap

CVE-2023-32973

HIGH · 7.2 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 4.5.4.2467 / 5.0.1.2425 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 buffer copy without checking size of input vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated administrators to execute code via a network. 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.0.1.2515 build 20230907 and later QuTS hero h5.1.0.2424 build 20230609 and later QuTS hero h4.5.4.2476 build 20230728 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 · high confidence

A buffer overflow vulnerability in QNAP operating systems allows authenticated administrators to execute arbitrary code via network by exploiting insufficient size checking during buffer copy operations. The vulnerability has a CVSS score of 7.2 (HIGH) and requires administrative-level access for exploitation.

MitigationUpdate affected QNAP devices to one of the fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, QTS 4.5.4.2467+, QuTS hero variants, or QuTScloud c5.1.0.2498+) and limit administrative access to trusted personnel only.

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.2467>= 5.0.0.1716, < 5.0.1.2425>= 5.1.0, < 5.1.0.2444
Quts HeroOperating system
Affected:>= h4.5.0, < h4.5.4.2476>= h5.0.0, < h5.0.1.2515>= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify the QNAP product type
    Determine whether the device runs QTS, QuTS Hero, or QuTScloud. This is typically visible in the system dashboard or login screen of the QNAP device.
    Affected if The device is running QTS, QuTS Hero, or QuTScloud.
  2. Check the installed firmware version
    Locate the firmware version in the QNAP admin interface (usually under Control Panel > System > Firmware) or via the q CLI tool if available.
    Affected if A firmware version is installed.
  3. Compare QTS version against affected ranges
    If the product is QTS, compare the installed version against these affected ranges: 4.5.1 to 4.5.4.2467 (exclusive), 5.0.0.1716 to 5.0.1.2425 (exclusive), or 5.1.0 to 5.1.0.2444 (exclusive).
    Affected if The installed QTS version falls within any of these ranges: >= 4.5.1 and < 4.5.4.2467; OR >= 5.0.0.1716 and < 5.0.1.2425; OR >= 5.1.0 and < 5.1.0.2444.
  4. Compare QuTS Hero version against affected ranges
    If the product is QuTS Hero, compare the installed version against these affected ranges: h4.5.0 to h4.5.4.2476 (exclusive), h5.0.0 to h5.0.1.2515 (exclusive), or h5.1.0 to h5.1.0.2424 (exclusive).
    Affected if The installed QuTS Hero version falls within any of these ranges: >= h4.5.0 and < h4.5.4.2476; OR >= h5.0.0 and < h5.0.1.2515; OR >= h5.1.0 and < h5.1.0.2424.
  5. Compare QuTScloud version against affected ranges
    If the product is QuTScloud, compare the installed version against this affected range: c5.0.0.1919 to c5.1.0.2498 (exclusive).
    Affected if The installed QuTScloud version is >= c5.0.0.1919 and < c5.1.0.2498.

The device is affected if it runs QTS, QuTS Hero, or QuTScloud with a firmware version that falls within any of the specified vulnerable ranges and the attacker has administrative access to the device.

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

Update affected QNAP devices to one of the fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, QTS 4.5.4.2467+, QuTS hero variants, or QuTScloud c5.1.0.2498+) and limit administrative access to trusted personnel only.

Recommended fix High confidence

QTS 4.5.4.2467 (build 20230718), QTS 5.0.1.2425 (build 20230609), QTS 5.1.0.2444 (build 20230629); QuTS hero h4.5.4.2476 (build 20230728), h5.0.1.2515 (build 20230907), h5.1.0.2424 (build 20230609); QuTScloud c5.1.0.2498 - depending on current major version

  1. Identify the current QTS, QuTS hero, or QuTScloud version and build number from the NAS Control Panel
  2. Determine the appropriate upgrade target based on current version: For QTS 4.5.1-4.5.4.x, upgrade to QTS 4.5.4.2467 build 20230718 or later; For QTS 5.0.0.x-5.0.1.x, upgrade to QTS 5.0.1.2425 build 20230609 or later; For QTS 5.1.0.x, upgrade to QTS 5.1.0.2444 build 20230629 or later; For QuTS hero h4.5.0-h4.5.4.x, upgrade to h4.5.4.2476 build 20230728 or later; For QuTS hero h5.0.0-h5.0.1.x, upgra
  3. Review the QNAP release notes for any compatibility warnings or breaking changes before upgrading
  4. Back up critical data on the NAS as a precautionary measure
  5. Access QNAP App Center or use the Firmware Updates utility to install the appropriate fixed version
  6. After upgrade, verify the build number matches or exceeds the fixed version to confirm remediation
Caveat Review QNAP release notes for application and hardware compatibility before upgrading; major version jumps may affect installed apps

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