dbcve.org
QtsOperating system · Qnap

CVE-2023-23369

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-03
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: Multimedia Console 2.1.2 ( 2023/05/04 ) and later Multimedia Console 1.4.8 ( 2023/05/05 ) and later QTS 5.1.0.2399 build 20230515 and later QTS 4.3.6.2441 build 20230621 and later QTS 4.3.4.2451 build 20230621 and later QTS 4.3.3.2420 build 20230621 and later QTS 4.2.6 build 20230621 and later Media Streaming add-on 500.1.1.2 ( 2023/06/12 ) and later Media Streaming add-on 500.0.0.11 ( 2023/06/16 ) 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 a critical OS command injection vulnerability in QNAP QTS and Multimedia Console that allows remote attackers to execute arbitrary commands via network. The vulnerability stems from insufficient input validation in the affected components, enabling attackers to inject OS commands through the interface.

MitigationImmediately update affected QNAP devices to one of the listed fixed versions (QTS builds 20230621 or later, Multimedia Console 1.4.8/2.1.2 or later). For systems awaiting updates, restrict network access to management interfaces and implement firewall rules limiting exposure to trusted IP addresses.

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= 4.3.6.0895= 4.3.6.0907= 4.3.6.0923= 4.3.6.0944= 4.3.6.0959= 4.3.6.0979= 4.3.6.0993= 4.3.6.1013= 4.3.6.1033= 4.3.6.1070= 4.3.6.1154
Multimedia ConsoleApplication
Affected:= 2.1.0= 2.1.1= 1.4.3= 1.4.4= 1.4.5= 1.4.6= 1.4.7
Media Streaming Add OnPlugin / extension
Affected:= 500.1.1.0= 500.1.1.1= 500.0.0.0= 500.0.0.1= 500.0.0.3= 500.0.0.4= 500.0.0.5= 500.0.0.6= 500.0.0.7= 500.0.0.8= 500.0.0.9= 500.0.0.10

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. Check QTS firmware version
    Access the QNAP admin console and navigate to Control Panel > System > Firmware, or use the command line and check /etc/config/default/version or the output of 'qm version' if available via SSH
    Affected if The installed QTS version is 5.1.0.2348 or any version in the 4.3.6 series from 0895 through 1154 (inclusive)
  2. Check Multimedia Console app version
    Open the QTS App Center, locate Multimedia Console, and view the installed version details; alternatively, check the application's version file if accessible via file browser or SSH
    Affected if The installed Multimedia Console version is 2.1.0, 2.1.1, or any version from 1.4.3 through 1.4.7 (inclusive)
  3. Check Media Streaming Add-On version
    Open the QTS App Center, locate Media Streaming Add-On, and view the installed version details; or check the app version via QNAP CLI tools if available
    Affected if The installed Media Streaming Add-On version matches any of these: 500.1.1.0, 500.1.1.1, 500.0.0.0, 500.0.0.1, 500.0.0.3, 500.0.0.4, 500.0.0.5, 500.0.0.6, 500.0.0.7, 500.0.0.8, 500.0.0.9, or 500.0.0.10

If any of the three components (QTS firmware, Multimedia Console, or Media Streaming Add-On) matches an affected version listed above, the system is vulnerable to command injection and should be updated immediately.

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

Immediately update affected QNAP devices to one of the listed fixed versions (QTS builds 20230621 or later, Multimedia Console 1.4.8/2.1.2 or later). For systems awaiting updates, restrict network access to management interfaces and implement firewall rules limiting exposure to trusted IP addresses.

Recommended fix High confidence

QTS 5.1.0.2399 (build 20230515) or later for QTS 5.x; QTS 4.3.6.2441 (build 20230621) or later for QTS 4.3.6; Multimedia Console 2.1.2 or later; Media Streaming Add-On 500.1.1.2 or later

  1. 1. Identify the exact QNAP product and current firmware version installed by accessing the QNAP admin interface or using the qnaputil command line tool.
  2. 2. Determine which affected component is running: QTS operating system, Multimedia Console app, or Media Streaming add-on.
  3. 3. For QTS systems: Access the QNAP Admin Panel, navigate to Control Panel > System > Firmware Update, and update to the appropriate fixed version based on your current branch (4.2.6, 4.3.3, 4.3.4, 4.3.6, or 5.1.0).
  4. 4. For Multimedia Console: Open App Center, locate Multimedia Console, and update to version 2.1.2 or later (or 1.4.8 or later depending on your major version).
  5. 5. For Media Streaming Add-On: Open App Center, locate Media Streaming Add-On, and update to version 500.1.1.2 or later (or 500.0.0.11 or later depending on your branch).
  6. 6. After updating, verify the new version is installed and restart the NAS if prompted.
  7. 7. Confirm the vulnerability is remediated by checking the QNAP security advisory for your specific version.
Caveat Standard QNAP firmware updates may cause temporary service interruptions; backup critical data 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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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