dbcve.org
QtsOperating system · Qnap

CVE-2023-23368

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
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.0.1.2376 build 20230421 and later QTS 4.5.4.2374 build 20230416 and later QuTS hero h5.0.1.2376 build 20230421 and later QuTS hero h4.5.4.2374 build 20230417 and later QuTScloud c5.0.1.2374 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

An OS command injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud allows remote attackers to execute arbitrary operating system commands via network by injecting malicious commands through unsanitized input vectors in the affected QNAP firmware versions.

MitigationUpdate QNAP devices to the fixed QTS, QuTS hero, or QuTScloud versions specified in the advisory. If immediate patching is not possible, restrict network access to management interfaces and disable unnecessary external services.

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.0.1= 5.0.1.2034= 5.0.1.2079= 5.0.1.2131= 5.0.1.2137= 5.0.1.2145= 5.0.1.2173= 5.0.1.2194= 5.0.1.2234= 5.0.1.2248= 5.0.1.2277= 5.0.1.2346
Quts HeroOperating system
Affected:= h5.0.1.2045= h5.0.1.2192= h5.0.1.2248= h5.0.1.2269= h5.0.1.2277= h5.0.1.2348= h4.5.4.1771= h4.5.4.1800= h4.5.4.1813= h4.5.4.1848= h4.5.4.1892= h4.5.4.1951
QutscloudOperating system
Affected:= c5.0.1.1949= c5.0.1.1998= c5.0.1.2044= c5.0.1.2148

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 QNAP product and firmware version
    Log into the QNAP device admin console and navigate to Control Panel > System > Firmware Update > firmware status, or use the command 'getconf' via SSH to retrieve the firmware version
    Affected if The product is QTS, QuTS hero, or QuTScloud and the version matches any of the specific builds listed in the affected versions (e.g., QTS 5.0.1.2234, QuTS hero h5.0.1.2248, or QuTScloud c5.0.1.2148)
  2. Confirm QTS version if applicable
    In the admin console, go to Control Panel > System > Firmware Update and note the exact build number shown (format: 5.0.1.xxxx)
    Affected if The version equals any of these: 5.0.1.2034, 5.0.1.2079, 5.0.1.2131, 5.0.1.2137, 5.0.1.2145, 5.0.1.2173, 5.0.1.2194, 5.0.1.2234, 5.0.1.2248, 5.0.1.2277, 5.0.1.2346
  3. Confirm QuTS hero version if applicable
    In the admin console, go to Control Panel > System > Firmware Update and note the exact build number shown (format: h5.0.1.xxxx or h4.5.4.xxxx)
    Affected if The version equals any of these: h5.0.1.2045, h5.0.1.2192, h5.0.1.2248, h5.0.1.2269, h5.0.1.2277, h5.0.1.2348, h4.5.4.1771, h4.5.4.1800, h4.5.4.1813, h4.5.4.1848, h4.5.4.1892, h4.5.4.1951
  4. Confirm QuTScloud version if applicable
    Check the QuTScloud version through the cloud portal or via the local management interface noting the build number (format: c5.0.1.xxxx)
    Affected if The version equals any of these: c5.0.1.1949, c5.0.1.1998, c5.0.1.2044, c5.0.1.2148
  5. Assess network exposure of management interface
    Check firewall rules, NAT configurations, or port forwarding settings to determine if the QNAP admin web interface (ports 80, 443, 8080, 8081) is accessible from untrusted networks or the public internet
    Affected if The management interface is exposed to the internet or untrusted LAN segments, which would allow remote attackers to inject commands

The device is affected if it runs any of the listed firmware versions AND the management interface is network-accessible to attackers.

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 the fixed QTS, QuTS hero, or QuTScloud versions specified in the advisory. If immediate patching is not possible, restrict network access to management interfaces and disable unnecessary external services.

Recommended fix High confidence

QTS 5.0.1.2376 (build 20230421) or later; QTS 4.5.4.2374 (build 20230416) or later; QuTS hero h5.0.1.2376 (build 20230421) or later; QuTS hero h4.5.4.2374 (build 20230417) or later; QuTScloud c5.0.1.2374 or later

  1. 1. Identify the current QNAP firmware version by accessing the QTS/QuTS hero/QuTScloud admin console and navigating to Control Panel > System > Firmware Update
  2. 2. Back up all critical data and configurations before performing the upgrade
  3. 3. For QTS 5.0.x users: Upgrade to QTS 5.0.1.2376 build 20230421 or later
  4. 4. For QTS 4.5.x users: Upgrade to QTS 4.5.4.2374 build 20230416 or later
  5. 5. For QuTS hero h5.0.x users: Upgrade to QuTS hero h5.0.1.2376 build 20230421 or later
  6. 6. For QuTS hero h4.5.x users: Upgrade to QuTS hero h4.5.4.2374 build 20230417 or later
  7. 7. For QuTScloud users: Upgrade to QuTScloud c5.0.1.2374 or later
  8. 8. Access the Firmware Update section and select 'Check for Update' to download and install the appropriate version
Caveat Standard QNAP firmware upgrade risks apply - ensure backups before proceeding

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 help mitigating

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