dbcve.org
QtsOperating system · Qnap

CVE-2023-34974

HIGH · 8.8 CVSS v3.1 Published 2024-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 several QNAP operating system versions. If exploited, the vulnerability could allow users to execute commands via a network. QuTScloud, QVR, QES are not affected. We have already fixed the vulnerability in the following versions: QTS 4.5.4.2790 build 20240605 and later QuTS hero h4.5.4.2626 build 20231225 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

OS command injection vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated or unauthenticated users to execute arbitrary commands via network by injecting shell metacharacters into user input that gets passed to system() or similar functions without proper sanitization.

MitigationApply the vendor-supplied firmware updates (QTS 4.5.4.2790 build 20240605 or later, QuTS hero h4.5.4.2626 build 20231225 or later). For systems that cannot be immediately patched, restrict network access to management interfaces and implement WAF rules to detect command injection patterns.

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.1715= 4.5.4.1723= 4.5.4.1741= 4.5.4.1787= 4.5.4.1800= 4.5.4.1892= 4.5.4.1931= 4.5.4.2012= 4.5.4.2117= 4.5.4.2280= 4.5.4.2374= 4.5.4.2467
Quts HeroOperating system
Affected:= h4.5.4.1771= h4.5.4.1800= h4.5.4.1813= h4.5.4.1848= h4.5.4.1892= h4.5.4.1951= h4.5.4.1971= h4.5.4.1991= h4.5.4.2052= h4.5.4.2138= h4.5.4.2217= h4.5.4.2272

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. Check QTS version via web interface
    Log into the QNAP admin web interface, go to Control Panel > System > Firmware/About, and note the Build Number and Version displayed
    Affected if The version shown matches any of: 4.5.4.1715, 4.5.4.1723, 4.5.4.1741, 4.5.4.1787, 4.5.4.1800, 4.5.4.1892, 4.5.4.1931, 4.5.4.2012, 4.5.4.2117, 4.5.4.2280, 4.5.4.2374, or 4.5.4.2467
  2. Check QTS version via command line
    Access the device via SSH or terminal and run: `cat /etc/uuid` or check the firmware version with `固件版本` or look at the banner on login
    Affected if The reported version matches any of the affected QTS versions listed above
  3. Check QuTS hero version via web interface
    Log into the QuTS hero admin web interface, navigate to Control Panel > System > Firmware/About, and record the Build Number and Version
    Affected if The version shown matches any of: h4.5.4.1771, h4.5.4.1800, h4.5.4.1813, h4.5.4.1848, h4.5.4.1892, h4.5.4.1951, h4.5.4.1971, h4.5.4.1991, h4.5.4.2052, h4.5.4.2138, h4.5.4.2217, or h4.5.4.2272
  4. Check QuTS hero version via command line
    Access the device via SSH or terminal and run: `cat /etc/uuid` or check the firmware version from the login banner or with `固件版本`
    Affected if The reported version matches any of the affected QuTS hero versions listed above

If the installed QTS or QuTS hero version matches any version in the affected list, the system is vulnerable to command injection and should be updated.

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

Apply the vendor-supplied firmware updates (QTS 4.5.4.2790 build 20240605 or later, QuTS hero h4.5.4.2626 build 20231225 or later). For systems that cannot be immediately patched, restrict network access to management interfaces and implement WAF rules to detect command injection patterns.

Recommended fix High confidence

QTS 4.5.4.2790 build 20240605 or later; QuTS hero h4.5.4.2626 build 20231225 or later

  1. 1. Identify your QNAP device model and current firmware version (check System Settings > Firmware Update)
  2. 2. Confirm the affected version matches your current QTS or QuTS hero installation
  3. 3. Download the appropriate firmware update: QTS 4.5.4.2790 build 20240605 (or later) for QTS devices, or QuTS hero h4.5.4.2626 build 20231225 (or later) for QuTS hero devices
  4. 4. Access QNAP Device Center or use the QNAP Qfinder Pro tool to perform the firmware update
  5. 5. After reboot, verify the new firmware version is installed and the vulnerability is resolved
  6. 6. Confirm that QuTScloud, QVR, and QES are not impacted (these are explicitly not affected per vendor)
Caveat Review QNAP release notes for any breaking changes or feature modifications before upgrading production systems

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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