CVE-2023-50358

QTS, QuTS hero, QuTScloud

MEDIUM
5.8
CVSS Score
Published: February 13, 2024 at 02:45 AM UTC
Updated: June 17, 2026 at 06:39 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
MEDIUM5.8
Exploit prediction
EPSS 14%
SSVC
No known exploit

Description

An OS command injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to execute commands via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.5.2645 build 20240116 and later QTS 4.5.4.2627 build 20231225 and later QTS 4.3.6.2665 build 20240131 and later QTS 4.3.4.2675 build 20240131 and later QTS 4.3.3.2644 build 20240131 and later QTS 4.2.6 build 20240131 and later QuTS hero h5.1.5.2647 build 20240118 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 and later

Affected

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

4.2.0 ≤ v < 4.2.64.2.x ≤ v < 4.2.6 build 202401314.3.0 ≤ v < 4.3.3.26444.3.4 ≤ v < 4.3.4.26754.3.4 ≤ v < 4.3.4.2675 build 202401314.3.5 ≤ v < 4.3.6.26654.3.6, 4.3.5 ≤ v < 4.3.6.2665 build 202401314.3.x ≤ v < 4.3.3.2644 build 202401314.5.1 ≤ v < 4.5.4.26274.5.x, 4.4.x ≤ v < 4.5.4.2627 build 202312255.1.0 ≤ v < 5.1.5.26455.x ≤ v < 5.1.5.2645 build 202401164.2.64.2.6 build_201705174.2.6 build_201903224.2.6 build_201907304.2.6 build_201909214.2.6 build_201911074.2.6 build_202001094.2.6 build_202004214.2.6 build_202006114.2.6 build_202008214.2.6 build_202103274.2.6 build_202112154.2.6 build_202203044.2.6 build_202206234.2.6 build_202210284.2.6 build_202306214.2.x4.3.44.3.54.3.64.3.x4.4.x4.5.4.26274.5.x5.1.5.26455.x
Affected range stops below 4.2.6 build 20240131, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.3.2644 build 20240131, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.4.2675 build 20240131, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.6.2665 build 20240131, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.4.2627 build 20231225, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.1.5.2645 build 20240116, so it looks safe — our inference, not a vendor statement
h4.5.0 ≤ v < h4.5.4.2626h4.x ≤ v < h4.5.4.2626 build 20231225h5.0.0 ≤ v < h5.1.5.2647h5.x ≤ v < h5.1.5.2647 build 20240118h4.5.4.2626h4.xh5.1.5.2647h5.x
Affected range stops below h4.5.4.2626 build 20231225, so it looks safe — our inference, not a vendor statement
Affected range stops below h5.1.5.2647 build 20240118, so it looks safe — our inference, not a vendor statement
c5.0.0.1919 ≤ v < c5.1.5.2651c5.x ≤ v < c5.1.5.2651c5.x
Affected range stops below c5.1.5.2651, 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

5.8MEDIUMqnap
Attack Vector
ADJACENT_NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-78

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