dbcve.org
QtsOperating system · Qnap

CVE-2023-39302

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.3.2578 build 20231110 and later QuTS hero h5.1.3.2578 build 20231110 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 allowing authenticated administrators to execute arbitrary commands via network. The vulnerability has a CVSS 7.2 (HIGH) rating due to the potential for complete system compromise through authenticated command execution.

MitigationUpdate to QTS 5.1.3.2578 build 20231110, QuTS hero h5.1.3.2578 build 20231110, or QuTScloud c5.1.5.2651 and later. Until patched, limit administrative access to trusted users only and apply network segmentation.

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:= 5.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.1.0.2444= 5.1.0.2466= 5.1.1.2491= 5.1.2.2533= 5.1.3.2578
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.1.0.2424= h5.1.0.2453= h5.1.0.2466= h5.1.1.2488= h5.1.2.2534= h5.1.3.2578
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 operating system product
    Log into the QNAP admin interface and check the System Information page, or run 'getsysinfo' via SSH to identify whether the system runs QTS, QuTS hero, or QuTScloud
    Affected if The system is running QTS, QuTS hero, or QuTScloud
  2. Retrieve the QTS/QuTS hero build version
    Run the command 'getsysinfo' via SSH or access the admin panel to view the exact build number displayed in System Information > Firmware Version
    Affected if The build number matches one of these QTS builds: 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444, 5.1.0.2466, 5.1.1.2491, 5.1.2.2533, 5.1.3.2578 OR one of these QuTS hero builds: h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1.2.2534, h5.1.3.2578
  3. Retrieve the QuTScloud version
    Access the QuTScloud console or admin interface and locate the firmware or system version information
    Affected if The version is c5.1.0.2498
  4. Confirm administrator access exists
    Verify whether valid administrator credentials can be obtained or whether the admin interface is exposed to the network
    Affected if An attacker with administrator credentials could reach the QTS/QuTS hero/QuTScloud admin interface (typically on ports 8080 or 443)

The system is affected if it runs QTS, QuTS hero, or QuTScloud and the installed build matches any of the specific vulnerable versions listed for that product.

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

Update to QTS 5.1.3.2578 build 20231110, QuTS hero h5.1.3.2578 build 20231110, or QuTScloud c5.1.5.2651 and later. Until patched, limit administrative access to trusted users only and apply network segmentation.

Recommended fix High confidence

QTS 5.1.3.2578 (build 20231110) / QuTS hero h5.1.3.2578 (build 20231110) / QuTScloud c5.1.5.2651

  1. 1. Back up all critical data and configurations on the QNAP device
  2. 2. Verify current firmware version in Control Panel > System > Firmware Update
  3. 3. For QTS users: Upgrade to QTS 5.1.3.2578 (build 20231110) or later
  4. 4. For QuTS hero users: Upgrade to h5.1.3.2578 (build 20231110) or later
  5. 5. For QuTScloud users: Upgrade to c5.1.5.2651 or later
  6. 6. Access the firmware update section via Control Panel > System > Firmware Update or use Qfinder Pro
  7. 7. Download and install the appropriate fixed firmware version
  8. 8. After upgrade, verify the system is functioning normally and the vulnerability is resolved
Caveat Standard firmware upgrade risks apply - ensure backups before proceeding; some settings may reset to defaults

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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