dbcve.org
QvrApplication · Qnap

CVE-2023-23355

HIGH · 7.2 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 5.0.1.2346 or later.
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 QNAP operating systems. If exploited, the vulnerability possibly allows remote authenticated administrators to execute commands via unspecified vectors. QES is not affected. We have already fixed the vulnerability in the following versions: QTS 5.0.1.2346 build 20230322 and later QTS 4.5.4.2374 build 20230416 and later QuTS hero h5.0.1.2348 build 20230324 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

OS command injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud allows remote authenticated administrators to execute arbitrary commands via unspecified vectors.

MitigationUpgrade to QTS 5.0.1.2346 or later (4.5.4 branch to 4.5.4.2374), QuTS hero h5.0.1.2348/h4.5.4.2374 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
QvrApplication
Affected:all versions
QtsOperating system
Affected:< 5.0.1.2346
Quts HeroOperating system
Affected:< h5.0.1.2348
QutscloudOperating system
Affected:all versions
Qvp 41b FirmwareOperating system
Affected:all versions
Qvp 63b FirmwareOperating system
Affected:all versions
Qvp 85b FirmwareOperating system
Affected:all versions
Qvp 21a FirmwareOperating system
Affected:all versions

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 QTS version
    Log into QNAP admin console and navigate to Control Panel > System > Firmware, or run the command 'cat /etc/config/qpkg.conf' or check the 'About' page in the UI to find the installed QTS version number
    Affected if Installed QTS version is lower than 5.0.1.2346 (e.g., 5.0.1.2xxx versions below 2346, or any 4.5.x version)
  2. Identify QuTS hero version
    Log into QuTS hero admin console and check System > Firmware > About, or run 'versus' command in CLI to display the firmware version
    Affected if Installed QuTS hero version is lower than h5.0.1.2348 (or h4.5.x versions below 2374)
  3. Identify QuTScloud version
    Check the QuTScloud appliance version through the cloud console or run 'cat /etc/os-release' in the CLI to find the build version
    Affected if Any QuTScloud version is installed (all versions are affected)
  4. Identify Qvr or Qvp firmware in use
    Check if QVR (QNAP VR) or QVP (QNAP Video Station) firmware packages are installed via App Center or by running 'ls /share/Web/ser2net' or checking installed QPKG packages
    Affected if Any QVR or QVP firmware version is installed (all versions of these products are affected)

User is affected if running QTS < 5.0.1.2346, QuTS hero < h5.0.1.2348, any QuTScloud version, or any Qvr/Qvp firmware version.

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 5.0.1.2346 or later
Fixed in 5.0.1.2346
Interim mitigation

Upgrade to QTS 5.0.1.2346 or later (4.5.4 branch to 4.5.4.2374), QuTS hero h5.0.1.2348/h4.5.4.2374 or later, or QuTScloud c5.0.1.2374 or later.

Recommended fix High confidence

QTS 5.0.1.2346+ / QTS 4.5.4.2374+ / QuTS hero h5.0.1.2348+ / QuTS hero h4.5.4.2374+ / QuTScloud c5.0.1.2374+ (depending on product line)

  1. 1. Identify the specific QNAP product (QTS, QuTS Hero, QuTScloud, or QVP firmware) and current firmware version in use
  2. 2. Access the QNAP admin interface and navigate to Control Panel > System Settings > Firmware Update
  3. 3. Determine the appropriate fixed version based on product type: For QTS 5.x, upgrade to 5.0.1.2346 build 20230322 or later; For QTS 4.5.x, upgrade to 4.5.4.2374 build 20230416 or later; For QuTS hero h5.x, upgrade to h5.0.1.2348 build 20230324 or later; For QuTS hero h4.5.x, upgrade to h4.5.4.2374 build 20230417 or later; For QuTScloud, upgrade to c5.0.1.2374 or later
  4. 4. Use the firmware update feature to download and apply the appropriate fixed version
  5. 5. After reboot, verify the new firmware version is installed by checking System Settings > Firmware Update
  6. 6. Confirm normal system operation after upgrade
Caveat Standard firmware update risks apply - ensure backups of critical data exist before upgrading, and schedule during maintenance window as update may require reboot

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

Fix this in Qvr Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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