dbcve.org
QtsOperating system · Qnap

CVE-2023-32972

HIGH · 7.2 CVSS v3.1 Published 2023-10-06
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 · moderate confidence

A buffer copy without checking size of input vulnerability exists in multiple QNAP OS versions, allowing authenticated administrators to execute arbitrary code via a network. This is a classic buffer overflow where the size of input data is not validated before copying into a fixed-size buffer, leading to memory corruption that can be leveraged for code execution.

MitigationUpdate affected QNAP systems (QTS, QuTS hero, QuTScloud) to the fixed versions listed. Since exploitation requires authenticated administrator access, ensure strong administrative credentials 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.0, < 4.5.4.2467>= 5.0.0, < 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.1, < 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 your QNAP NAS operating system
    Log into the QNAP admin web interface and check System > System Settings > General Settings, or use Qfinder Pro to identify the model and OS type (QTS, QuTS hero, or QuTScloud)
    Affected if The system is running QTS, QuTS hero, or QuTScloud
  2. Locate the installed firmware version
    In the QNAP admin interface, go to Control Panel > System > System Status > System Information to view the Firmware Version
    Affected if The firmware version displayed matches any of the affected version ranges for your OS type
  3. Compare QTS version against affected ranges
    If running QTS, note the version number (for example, 4.5.4.2450 or 5.0.1.2420) and check if it falls in: 4.5.0 to 4.5.4.2466, 5.0.0 to 5.0.1.2424, or 5.1.0 to 5.1.0.2443
    Affected if The installed QTS version is within any of these three ranges
  4. Compare QuTS hero version against affected ranges
    If running QuTS hero, note the version number (for example, h4.5.4.2470 or h5.0.1.2510) and check if it falls in: h4.5.0 to h4.5.4.2475, h5.0.0 to h5.0.1.2514, or h5.1.0 to h5.1.0.2423
    Affected if The installed QuTS hero version is within any of these three ranges
  5. Compare QuTScloud version against affected ranges
    If running QuTScloud, note the version number (for example, c5.0.1.2490) and check if it falls in: c5.0.1 to c5.1.0.2497
    Affected if The installed QuTScloud version is within this range

You are affected if your QNAP device runs QTS, QuTS hero, or QuTScloud and the installed firmware version falls within any of the vulnerable version ranges for that product.

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 systems (QTS, QuTS hero, QuTScloud) to the fixed versions listed. Since exploitation requires authenticated administrator access, ensure strong administrative credentials and limit administrative access to trusted personnel only.

Recommended fix High confidence

QTS: 4.5.4.2467 / 5.0.1.2425 / 5.1.0.2444; QuTS hero: h4.5.4.2476 / h5.0.1.2515 / h5.1.0.2424; Qutscloud: c5.1.0.2498

  1. 1. Identify the current QNAP product and version (QTS, QuTS hero, or Qutscloud) by accessing the QNAP admin interface and checking System Settings > Firmware/Version
  2. 2. For QTS systems: If running version 4.5.0-4.5.4.2466, upgrade to QTS 4.5.4.2467 or later; if running 5.0.0-5.0.1.2424, upgrade to QTS 5.0.1.2425 or later; if running 5.1.0-5.1.0.2443, upgrade to QTS 5.1.0.2444 or later
  3. 3. For QuTS hero systems: If running h4.5.0-h4.5.4.2475, upgrade to QuTS hero h4.5.4.2476 or later; if running h5.0.0-h5.0.1.2514, upgrade to QuTS hero h5.0.1.2515 or later; if running h5.1.0-h5.1.0.2423, upgrade to QuTS hero h5.1.0.2424 or later
  4. 4. For Qutscloud systems: If running c5.0.1-c5.1.0.2497, upgrade to Qutscloud c5.1.0.2498 or later
  5. 5. Download the appropriate firmware from the QNAP download center (download.qnap.com) matching your specific model and product line
  6. 6. Perform the firmware upgrade via Control Panel > System > Firmware Update, or use the QNAP Finder tool for offline firmware update
  7. 7. After upgrade completes, verify the new version by checking System Settings > Firmware/Version and confirm it matches or exceeds the fixed build numbers
Caveat Firmware upgrades carry inherent risk of disruption; ensure critical data is backed up before proceeding; some legacy applications may require reinstallation after major version jumps

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
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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