CVE-2023-32971

QTS, QuTS hero, QuTScloud

HIGH
7.2
CVSS Score
Published: October 6, 2023 at 04:36 PM UTC
Updated: June 17, 2026 at 05:59 AM UTC
3 products affected across 1 vendorQTSQuTS heroQuTScloud

Using QTS by QNAP Systems Inc.?

Get instant alerts when new vulnerabilities affect QTS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.2
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.5.0 ≤ v < 4.5.4.24674.5.x ≤ v < 4.5.4.2467 build 202307185.0.0 ≤ v < 5.0.1.24255.0.x ≤ v < 5.0.1.2425 build 202306095.1.0 ≤ v < 5.1.0.24445.1.x ≤ v < 5.1.0.2444 build 202306294.5.x5.0.x5.1.x
Affected range stops below 4.5.4.2467, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.4.2467 build 20230718, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.1.2425, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.1.2425 build 20230609, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.1.0.2444, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.1.0.2444 build 20230629, so it looks safe — our inference, not a vendor statement
h4.5.0 ≤ v < h4.5.4.2476h4.5.x ≤ v < h4.5.4.2476 build 20230728h5.0.0 ≤ v < h5.0.1.2515h5.0.x ≤ v < h5.0.1.2515 build 20230907h5.1.0 ≤ v < h5.1.0.2424h5.1.x ≤ v < h5.1.0.2424 build 20230609h4.5.xh5.0.xh5.1.x
Affected range stops below h4.5.4.2476, so it looks safe — our inference, not a vendor statement
Affected range stops below h4.5.4.2476 build 20230728, so it looks safe — our inference, not a vendor statement
Affected range stops below h5.0.1.2515, so it looks safe — our inference, not a vendor statement
Affected range stops below h5.0.1.2515 build 20230907, so it looks safe — our inference, not a vendor statement
Affected range stops below h5.1.0.2424, so it looks safe — our inference, not a vendor statement
Affected range stops below h5.1.0.2424 build 20230609, so it looks safe — our inference, not a vendor statement
c5.0.1 ≤ v < c5.1.0.2498c5.0.x ≤ v < c5.1.0.2498c5.0.x
Affected range stops below c5.1.0.2498, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-120CWE-121CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card