dbcve.org
QtsOperating system · Qnap

CVE-2023-45025

CRITICAL · 9.8 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 →
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.1.4.2596 build 20231128 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.4.2596 build 20231128 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

OS command injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems allows remote attackers to execute arbitrary commands via network. The flaw stems from insufficient input validation in affected components, enabling malicious input to be passed to system shell.

MitigationApply vendor-supplied patches: QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.4.2596+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+ depending on your deployment.

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
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 the QNAP product type
    Determine if the system is running QTS, QuTS hero, or QuTScloud. This can typically be found in the system information or about section of the QNAP admin interface.
    Affected if The system is any of the three affected product types: QTS, QuTS hero, or QuTScloud.
  2. Check the installed firmware version
    Locate the firmware or operating system version in the QNAP admin panel under System Settings > System > About, or via the CLI if accessible. Record the full version number including any prefix such as 'h' for QuTS hero or 'c' for QuTScloud.
    Affected if The version matches one of the specific affected versions listed for the product type.
  3. Compare against QTS affected versions
    If the product is QTS, compare the installed version (such as 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) against your installed version.
    Affected if The installed QTS version exactly matches any version in the list.
  4. Compare against QuTS hero affected versions
    If the product is QuTS hero, compare the installed version (such as 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) against your installed version.
    Affected if The installed QuTS hero version exactly matches any version in the list.
  5. Compare against QuTScloud affected versions
    If the product is QuTScloud, compare the installed version (c5.1.0.2498) against your installed version.
    Affected if The installed QuTScloud version is exactly c5.1.0.2498.
  6. Verify the network-exposed interface
    Confirm whether the QNAP admin interface or any QNAP web services are accessible from the network. The vulnerability is exploitable remotely via network access.
    Affected if The QNAP management interface is network-accessible and the version matches an affected version.

The system is affected if it runs QTS, QuTS hero, or QuTScloud and the installed version exactly matches one of the specific versions listed in the affected products and 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 vendor-supplied patches: QTS 5.1.4.2596+, QTS 4.5.4.2627+, QuTS hero h5.1.4.2596+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+ depending on your deployment.

Recommended fix High confidence

QTS 4.5.4.2627 (build 20231225) or later; QTS 5.1.4.2596 (build 20231128) or later; QuTS hero h4.5.4.2626 (build 20231225) or later; QuTS hero h5.1.4.2596 (build 20231128) or later; QuTScloud c5.1.5.2651 or later

  1. Verify current QNAP firmware version through the admin console or via `getcfg` command
  2. Identify the product line (QTS, QuTS hero, or QuTScloud) and current version from the affected versions list
  3. Access QNAP Admin Console (https://<device-ip>:8080)
  4. Navigate to Control Panel > System > Firmware Update
  5. Alternatively, use QNAP Finder to check for and apply updates
  6. Ensure backup of critical data before performing firmware update
  7. Select the appropriate fixed version: For QTS 4.5.x, upgrade to 4.5.4.2627 build 20231225 or later; For QTS 5.1.x, upgrade to 5.1.4.2596 build 20231128 or later; For QuTS hero h4.5.x, upgrade to h4.5.4.2626 build 20231225 or later; For QuTS hero h5.1.x, upgrade to h5.1.4.2596 build 20231128 or later; For QuTScloud, upgrade to c5.1.5.2651 or later
  8. Allow firmware update to complete and device to reboot
Caveat Review QNAP release notes for any configuration or feature changes between versions; ensure application compatibility before upgrading

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
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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