dbcve.org
QtsOperating system · Qnap

CVE-2023-47567

HIGH · 7.2 CVSS v3.1 Published 2024-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 authenticated administrators 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 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

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 authenticated administrator users to execute arbitrary operating system commands via network requests, potentially leading to complete system compromise.

MitigationApply the appropriate firmware update for your QNAP system version (QTS 5.1.5.2645+, QTS 4.5.4.2627+, QuTS hero h5.1.5.2647+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) to remediate this vulnerability.

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.2627
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
QutscloudOperating system
Affected:= c5.1.0.2498

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

CVSS:3.1/AV:N/AC:L/PR:H/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 type
    Log into the QNAP admin interface and navigate to Control Panel > System > System Status, or run 'getsysinfo' via CLI to determine if the system is running QTS, QuTS hero, or QuTScloud
    Affected if The system is QTS, QuTS hero, or QuTScloud
  2. Check the QTS version
    In QTS web interface, go to Control Panel > System > Firmware Update > Firmware Information, or run '/sbin/getcfg System.Version -d' via SSH
    Affected if The version 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.2627
  3. Check the QuTS hero version
    In QuTS hero web interface, go to Control Panel > System > Firmware Update > Firmware Information, or run '/sbin/getcfg System.Version -d' via SSH
    Affected if The version 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 the QuTScloud version
    Access the QuTScloud console or run 'version' command via CLI
    Affected if The version is c5.1.0.2498
  5. Verify administrator access exists
    Confirm that administrator accounts exist on the system and that the web management interface is accessible over the network
    Affected if The system has administrator accounts and is network-accessible (since authenticated admin required for exploitation)

The system is affected if it runs QTS, QuTS hero, or QuTScloud with any of the specific versions listed in the affected product versions.

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 appropriate firmware update for your QNAP system version (QTS 5.1.5.2645+, QTS 4.5.4.2627+, QuTS hero h5.1.5.2647+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) to remediate this vulnerability.

Recommended fix High confidence

QTS 4.5.4.2627+ (build 20231225) / QTS 5.1.5.2645+ (build 20240116) / QuTS hero h4.5.4.2626+ (build 20231225) / QuTS hero h5.1.5.2647+ (build 20240118) / QuTScloud c5.1.5.2651+ depending on product line

  1. 1. Back up all critical data and configurations on the QNAP device
  2. 2. Identify the current QNAP OS version (QTS, QuTS hero, or QuTScloud) from the System Administration > Firmware page
  3. 3. For QTS 4.5.x users: Upgrade to QTS 4.5.4.2627 build 20231225 or later
  4. 4. For QTS 5.x users: Upgrade to QTS 5.1.5.2645 build 20240116 or later
  5. 5. For QuTS hero h4.5.x users: Upgrade to QuTS hero h4.5.4.2626 build 20231225 or later
  6. 6. For QuTS hero h5.x users: Upgrade to QuTS hero h5.1.5.2647 build 20240118 or later
  7. 7. For QuTScloud users: Upgrade to QuTScloud c5.1.5.2651 or later
  8. 8. Verify the upgrade was successful by checking the firmware version after reboot
Caveat Standard QNAP firmware upgrade - review release notes for any feature changes; backup recommended before any firmware update

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