dbcve.org
Video StationApplication · Qnap

CVE-2023-34975

HIGH · 8.8 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 5.7.0 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 several QNAP operating system versions. If exploited, the vulnerability could allow authenticated administrators to execute commands via a network. QuTScloud is not affected. We have already fixed the vulnerability in the following versions: QuTS hero h4.5.4.2626 build 20231225 and later QTS 4.5.4.2627 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 administrators to execute arbitrary operating system commands via network. The vulnerability is fixed in QTS 4.5.4.2627 and QuTS hero h4.5.4.2626 (build 20231225 and later).

MitigationUpdate affected QNAP devices to QTS 4.5.4.2627 or QuTS hero h4.5.4.2626 (or later) from build 20231225. QuTScloud is not affected by 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
Video StationApplication
Affected:< 5.7.0

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. Verify Video Station is installed
    Log into QTS/QuTS hero as administrator, open App Center, and look for Video Station in the installed applications list. Alternatively, run the command: cat /share/CACHEDEV1_DATA/.qpkg/VideoStation/.qpkg.xml 2>/dev/null || echo 'Not found'
    Affected if Video Station is present on the system
  2. Determine Video Station version
    In App Center, click on Video Station and view the version number shown. From command line, run: cat /share/CACHEDEV1_DATA/.qpkg/VideoStation/.qpkg.xml 2>/dev/null | grep -i version
    Affected if The displayed version is lower than 5.7.0
  3. Confirm QTS or QuTS hero build date
    Log into QNAP admin interface, go to System Settings > System > System Information, or run command: getcfg System version
    Affected if Build date is before 20231225 (this indicates an unpatched QTS/QuTS hero version)
  4. Cross-check Video Station package file
    Check the package manifest file at /share/CACHEDEV1_DATA/.qpkg/VideoStation/package.xml for the <Version> tag value
    Affected if Version tag shows a number less than 5.7.0

The system is affected if QNAP Video Station version is installed and is lower than 5.7.0 on a QTS/QuTS hero system with build date before 20231225.

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.7.0 or later
Fixed in 5.7.0
Interim mitigation

Update affected QNAP devices to QTS 4.5.4.2627 or QuTS hero h4.5.4.2626 (or later) from build 20231225. QuTScloud is not affected by this vulnerability.

Recommended fix High confidence

QTS 4.5.4.2627 build 20231225 or later / QuTS hero h4.5.4.2626 build 20231225 or later

  1. 1. Back up all critical data and configurations on the QNAP device
  2. 2. Verify current QTS or QuTS hero version by navigating to Control Panel > System > Firmware Update
  3. 3. Download and install QTS 4.5.4.2627 build 20231225 or later (or QuTS hero h4.5.4.2626 build 20231225 or later)
  4. 4. After firmware update, verify Video Station has been updated to version 5.7.0 or later
  5. 5. Confirm the vulnerability is resolved by checking the QNAP security advisor or verifying the installed versions
Caveat Standard QNAP firmware update risks apply - ensure backup before upgrading; some settings may reset to defaults

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

Fix this in Video Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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