dbcve.org
QtsOperating system · Qnap

CVE-2023-32975

HIGH · 7.2 CVSS v3.1 Published 2023-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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.2514 build 20230906 and later QTS 5.1.2.2533 build 20230926 and later QuTS hero h5.0.1.2515 build 20230907 and later QuTS hero h5.1.2.2534 build 20230927 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

Buffer overflow vulnerability in QNAP QTS and QuTS hero operating systems where authenticated administrators could execute arbitrary code via network due to unsanitized buffer copy operation.

MitigationUpdate QNAP devices to QTS 5.0.1.2514 build 20230906 / 5.1.2.2533 build 20230926 or later, or QuTS hero h5.0.1.2515 build 20230907 / h5.1.2.2534 build 20230927 or later.

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.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.1.0.2444= 5.1.0.2466= 5.1.1.2491= 5.0.1.2034= 5.0.1.2079= 5.0.1.2131= 5.0.1.2137= 5.0.1.2145= 5.0.1.2173
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.1.0.2424= h5.1.0.2453= h5.1.0.2466= h5.1.1.2488= h5.0.1.2045= h5.0.1.2192= h5.0.1.2248= h5.0.1.2269= h5.0.1.2277= h5.0.1.2348= h5.0.1.2376

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 operating system type
    Log into the QNAP device and go to Control Panel > System > System Status, or check the login page banner for 'QTS' or 'QuTS hero'
    Affected if The system runs QTS or QuTS hero operating system
  2. Find the installed QTS version and build number
    Go to Control Panel > System > System Status > Firmware Version, or use the command 'getsysinfo' via SSH
    Affected if The version matches any of: 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444, 5.1.0.2466, 5.1.1.2491, 5.0.1.2034, 5.0.1.2079, 5.0.1.2131, 5.0.1.2137, 5.0.1.2145, 5.0.1.2173
  3. Find the installed QuTS hero version and build number
    Go to Control Panel > System > System Status > Firmware Version, or use the command 'getsysinfo' via SSH. Look for version numbers starting with 'h5'
    Affected if The version matches any of: h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.0.1.2045, h5.0.1.2192, h5.0.1.2248, h5.0.1.2269, h5.0.1.2277, h5.0.1.2348, h5.0.1.2376
  4. Confirm remote administrator access is enabled
    Check Control Panel > System > General Settings > Administration, verify if 'Allow system administrators to access via SSH' or 'Web server port' settings are enabled
    Affected if Remote administration (SSH/HTTPS/HTTP) is accessible from the network

The environment is affected if the device runs QTS or QuTS hero with a version or build number matching any of the listed affected versions, and remote administrator access is enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update QNAP devices to QTS 5.0.1.2514 build 20230906 / 5.1.2.2533 build 20230926 or later, or QuTS hero h5.0.1.2515 build 20230907 / h5.1.2.2534 build 20230927 or later.

Recommended fix High confidence

QTS 5.0.1.2514+ / QTS 5.1.2.2533+ / QuTS hero h5.0.1.2515+ / QuTS hero h5.1.2.2534+ depending on your current branch

  1. 1. Identify your current QTS or QuTS hero version in the System Administration > Firmware Update section of QNAP Control Panel.
  2. 2. If running QTS 5.0.x, upgrade to QTS 5.0.1.2514 build 20230906 or later.
  3. 3. If running QTS 5.1.x, upgrade to QTS 5.1.2.2533 build 20230926 or later.
  4. 4. If running QuTS hero h5.0.x, upgrade to QuTS hero h5.0.1.2515 build 20230907 or later.
  5. 5. If running QuTS hero h5.1.x, upgrade to QuTS hero h5.1.2.2534 build 20230927 or later.
  6. 6. After upgrade, verify the system is functioning normally and the new firmware version is applied.
Caveat Firmware upgrades carry inherent risks; ensure critical data is backed up before performing the upgrade

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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