dbcve.org
QtsOperating system · Qnap

CVE-2022-27596

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-30
Fix available
A fix is available. Upgrade to 5.0.1.2234 or later.
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
A vulnerability has been reported to affect QNAP device running QuTS hero, QTS. If exploited, this vulnerability allows remote attackers to inject malicious code. We have already fixed this vulnerability in the following versions of QuTS hero, QTS: QuTS hero h5.0.1.2248 build 20221215 and later QTS 5.0.1.2234 build 20221201 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 · moderate confidence

A remote code injection vulnerability in QNAP NAS devices running QuTS hero and QTS allows unauthenticated remote attackers to inject malicious code. The critical CVSS 9.8 score indicates the vulnerability is easily exploitable and can lead to complete system compromise.

MitigationUpdate QuTS hero to h5.0.1.2248 build 20221215 or later, or QTS to 5.0.1.2234 build 20221201 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
QtsOperating system
Affected:>= 5.0.1, < 5.0.1.2234
Quts HeroOperating system
Affected:>= h5.0.1, < h5.0.1.2248

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. Identify the QNAP NAS operating system
    Log into the QNAP admin interface and check System Information > Firmware Version, or run 'getsysinfo' via SSH to see if the OS is QTS or QuTS hero
    Affected if The device runs either QTS or QuTS hero operating system
  2. Determine the QTS firmware version
    In the admin interface, go to Control Panel > System > Firmware > Firmware Information to view the exact version number (for example, 5.0.1.2208)
    Affected if Running QTS version 5.0.1 or higher but lower than 5.0.1.2234
  3. Determine the QuTS hero firmware version
    In the admin interface, go to Control Panel > System > Firmware > Firmware Information to view the exact version (for example, h5.0.1.2208)
    Affected if Running QuTS hero version h5.0.1 or higher but lower than h5.0.1.2248
  4. Check network exposure of admin interface
    Verify if the QNAP admin portal (ports 808 or 443) is accessible from the internet or untrusted networks by reviewing router port forwarding rules or firewall settings
    Affected if The admin interface is directly exposed to the internet without VPN or proper access controls

A device is affected if it runs QTS below version 5.0.1.2234 or QuTS hero below version h5.0.1.2248, especially when the admin interface is network-accessible.

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.2234 or later
Fixed in 5.0.1.2234
Interim mitigation

Update QuTS hero to h5.0.1.2248 build 20221215 or later, or QTS to 5.0.1.2234 build 20221201 or later.

Recommended fix High confidence

QTS 5.0.1.2234 (build 20221201 or later) or QuTS hero h5.0.1.2248 (build 20221215 or later)

  1. 1. Identify the current QNAP device model and confirm the operating system (QTS or QuTS hero)
  2. 2. Check the current OS version in the QNAP admin interface under 'Control Panel' > 'System' > 'Firmware'
  3. 3. For QTS systems: Upgrade to QTS 5.0.1.2234 build 20221201 or later
  4. 4. For QuTS hero systems: Upgrade to QuTS hero h5.0.1.2248 build 20221215 or later
  5. 5. Download the appropriate firmware from the QNAP download center: https://download.qnap.com/
  6. 6. In the QNAP admin interface, navigate to 'Control Panel' > 'System' > 'Firmware Update'
  7. 7. Select 'Manual Firmware Update' and choose the downloaded firmware file
  8. 8. Wait for the firmware upload and installation to complete - do not power off the device

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

Fix this in Qts 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-2022-27596 — 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-2022-27596 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