dbcve.org
QtsOperating system · Qnap

CVE-2023-34979

HIGH · 7.2 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 →
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 4.5.4.2790 build 20240605 and later QuTS hero h4.5.4.2790 build 20240606 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 and QuTS hero operating systems that allows authenticated administrators to execute arbitrary commands via network. The vulnerability stems from improper input validation that enables command injection through the web interface or API.

MitigationApply the vendor-supplied firmware updates: QTS 4.5.4.2790 build 20240605 or later for QTS systems, and QuTS hero h4.5.4.2790 build 20240606 or later for QuTS hero systems. Ensure proper backup and maintenance window before applying updates.

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
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 operating system type
    Access the QNAP admin interface and check the system information page, or run 'getsysinfo' via QCLI/SSH to determine if the system is running QTS or QuTS hero
    Affected if The system is running QTS or QuTS hero operating system
  2. Check the installed QTS firmware version
    In the QTS admin console, go to Control Panel > System > Firmware Update > Check Firmware History, or access https://<device_ip>/cgi-bin/authLogin.cgi?authLogout=1 to retrieve version info via API, or run 'grep 'QTS' /etc/config/defalut/uBoot_image' 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.2467
  3. Check the installed QuTS hero firmware version
    In the QuTS hero admin console, go to Control Panel > System > Firmware Update > Check Firmware History, or run 'grep 'QuTS' /etc/config/defalut/uBoot_image' 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. Verify administrator access to web interface or API
    Attempt to access the QNAP web admin interface at port 8080 or 443, or test API endpoint availability at /cgi-bin/ with valid administrator credentials
    Affected if An authenticated administrator session can be established (this is required for the vulnerability to be exploitable)

The environment is affected if the device runs QTS version 4.5.4.1715 through 4.5.4.2467 or QuTS hero version h4.5.4.1771 through h4.5.4.2272 AND the web interface/API is accessible with administrator credentials.

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 for QTS systems, and QuTS hero h4.5.4.2790 build 20240606 or later for QuTS hero systems. Ensure proper backup and maintenance window before applying updates.

Recommended fix High confidence

QTS 4.5.4.2790 build 20240605 or later; QuTS hero h4.5.4.2790 build 20240606 or later

  1. 1. Identify whether the QNAP device is running QTS or QuTS hero by accessing the QNAP admin interface and checking the System Overview page
  2. 2. Note the current firmware version from the System Overview page
  3. 3. If running QTS, ensure current version is at least 4.5.4.2790 build 20240605; if running QuTS hero, ensure current version is at least h4.5.4.2790 build 20240606
  4. 4. If the current version is below the fixed versions, navigate to Control Panel > System > Firmware Update
  5. 5. Click 'Check for Update' to download and install the latest available firmware from QNAP
  6. 6. Alternatively, download the specific firmware file from the QNAP download center and manually update via 'Update manually' option
  7. 7. Allow the system to reboot after the firmware update completes
  8. 8. Verify the new firmware version matches or exceeds the fixed version numbers
Caveat Firmware updates on QNAP devices typically require a reboot and may have a brief downtime window; ensure backup of critical data before proceeding

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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