dbcve.org
QtsOperating system · Qnap

CVE-2023-23362

HIGH · 8.8 CVSS v3.1 Published 2023-09-22
Fix available
A fix is available. Upgrade to 4.5.4.2374 / 5.0.1.2376 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An OS command injection vulnerability has been reported to affect QNAP operating systems. If exploited, the vulnerability allows remote authenticated users to execute commands via susceptible QNAP devices. 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

This is an OS command injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems. The flaw allows remote authenticated users to execute arbitrary operating system commands on affected QNAP devices through unsanitized input being passed to system shell commands.

MitigationUpgrade affected QNAP devices to the fixed versions: 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, or QuTScloud c5.0.1.2374 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:>= 4.5.4, < 4.5.4.2374>= 5.0.1, < 5.0.1.2376
Quts HeroOperating system
Affected:>= h4.5.4, < h4.5.4.2374>= h5.0.1, < h5.0.1.2376
QutscloudOperating system
Affected:>= c5.0.1, <= c5.0.1.2374

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

CVSS:3.1/AV:N/AC:L/PR:L/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 product variant
    Log into the QNAP admin interface and locate the System Information page, or run `cat /proc/bootimg/rootfs_1/etc/version.build` from the command line to determine if the device runs QTS, QuTS hero, or QuTScloud
    Affected if The product is QTS, QuTS hero, or QuTScloud and the specific version falls within the affected ranges
  2. Check the installed QTS version
    In the QTS admin UI, go to Control Panel > System > Firmware > About, or run the command `getconf PATCH_VERSION` to retrieve the current firmware build number
    Affected if The version is QTS 4.5.4.x where x is less than 2374, or QTS 5.0.1.x where x is less than 2376
  3. Check the installed QuTS hero version
    In the QuTS hero admin UI, navigate to Control Panel > System > Firmware > About, or use the command line to retrieve the build version
    Affected if The version is QuTS hero h4.5.4.x where x is less than 2374, or QuTS hero h5.0.1.x where x is less than 2376
  4. Check the installed QuTScloud version
    Check the QuTScloud console or run the appropriate command to retrieve the firmware version
    Affected if The version is QuTScloud c5.0.1.x where x is 2374 or lower
  5. Verify remote authentication status
    Review the admin UI under Control Panel > Security > Firewall or system access settings to confirm whether remote administrative access is permitted
    Affected if Remote authenticated access is enabled, which is required for exploitation of this command injection flaw

A device is affected if it runs any of the affected QTS, QuTS hero, or QuTScloud versions within the specified vulnerable ranges and has remote authentication 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
Upgrade available Upgrade to 4.5.4.2374 / 5.0.1.2376 or later
Fixed in 4.5.4.23745.0.1.2376
Interim mitigation

Upgrade affected QNAP devices to the fixed versions: 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, or QuTScloud c5.0.1.2374 or later.

Recommended fix High confidence

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

  1. 1. Identify your QNAP device model and the operating system running on it (QTS, QuTS hero, or QuTScloud)
  2. 2. Check the current firmware version by logging into the QNAP admin interface and navigating to Control Panel > System > Firmware Update
  3. 3. For QTS users: If running version 4.5.4.x, upgrade to QTS 4.5.4.2374 (build 20230416) or later; if running 5.0.1.x, upgrade to QTS 5.0.1.2376 (build 20230421) or later
  4. 4. For QuTS hero users: If running h4.5.4.x, upgrade to QuTS hero h4.5.4.2374 (build 20230417) or later; if running h5.0.1.x, upgrade to QuTS hero h5.0.1.2376 (build 20230421) or later
  5. 5. For QuTScloud users: Upgrade to QuTScloud c5.0.1.2374 or later
  6. 6. Download the firmware update from the QNAP download center and apply via the firmware update utility
  7. 7. After upgrade, verify the new build number matches or exceeds the fixed version for your product line
Caveat Standard firmware upgrade risks apply - ensure data backup before upgrading; some settings may reset to defaults

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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