QtsOperating system · Qnap

CVE-2022-27600

HIGH · 7.5 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to 4.5.4.2280 / 5.0.1.2277 or later.
See remediation →
84/100
Remediation priority · High
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 uncontrolled resource consumption vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following versions: QTS 5.0.1.2277 and later QTS 4.5.4.2280 build 20230112 and later QuTS hero h5.0.1.2277 build 20230112 and later QuTS hero h4.5.4.2374 build 20230417 and later QuTScloud c5.0.1.2374 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

Uncontrolled resource consumption vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems allows remote unauthenticated attackers to exhaust system resources and cause denial of service.

MitigationApply available firmware updates (QTS 5.0.1.2277+, QTS 4.5.4.2280+, QuTS hero h5.0.1.2277+, QuTS hero h4.5.4.2374+, QuTScloud c5.0.1.2374+) to patched versions.

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.1, < 4.5.4.2280>= 5.0.0, < 5.0.1.2277= 4.5.4.2280= 5.0.1.2277
Quts HeroOperating system
Affected:>= h4.5.1, < h4.5.4.2374>= h5.0, < h5.0.1.2277= h4.5.4.2374= h5.0.1.2277
QutscloudOperating system
Affected:>= c5.0.1, < c5.0.1.2374

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 product type
    Log into the QNAP admin web interface and check System Settings > Firmware, or run `cat /etc/config/version` on the device to determine if the system is running QTS, QuTS hero, or QuTScloud.
    Affected if The product is QTS, QuTS hero, or QuTScloud.
  2. Determine the installed firmware version
    In the web UI, go to Control Panel > System > Firmware and note the exact version number displayed. Alternatively, run the command `getsysinfo` or check the file `/etc/config/version` on the device.
    Affected if The exact version cannot be determined from the system.
  3. Compare QTS version against affected ranges
    If running QTS, compare your version to these ranges: 4.5.1 to 4.5.4.2279, 5.0.0 to 5.0.1.2276, or specifically versions 4.5.4.2280 or 5.0.1.2277.
    Affected if The installed QTS version falls within or equals any of these: >=4.5.1 and <4.5.4.2280, >=5.0.0 and <5.0.1.2277, =4.5.4.2280, or =5.0.1.2277.
  4. Compare QuTS hero version against affected ranges
    If running QuTS hero, compare your version to these ranges: h4.5.1 to h4.5.4.2373, h5.0 to h5.0.1.2276, or specifically versions h4.5.4.2374 or h5.0.1.2277.
    Affected if The installed QuTS hero version falls within or equals any of these: >=h4.5.1 and <h4.5.4.2374, >=h5.0 and <h5.0.1.2277, =h4.5.4.2374, or =h5.0.1.2277.
  5. Compare QuTScloud version against affected ranges
    If running QuTScloud, compare your version to the range c5.0.1 to c5.0.1.2373.
    Affected if The installed QuTScloud version is >=c5.0.1 and <c5.0.1.2374.

The system is affected if the installed firmware version matches any of the specific affected versions or falls within any of the affected version ranges for QTS, QuTS hero, or QuTScloud as listed.

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 4.5.4.2280 / 5.0.1.2277 or later
Fixed in 4.5.4.22805.0.1.2277
Interim mitigation

Apply available firmware updates (QTS 5.0.1.2277+, QTS 4.5.4.2280+, QuTS hero h5.0.1.2277+, QuTS hero h4.5.4.2374+, QuTScloud c5.0.1.2374+) to patched versions.

Recommended fix High confidence

QTS 5.0.1.2277+ (build 20230112+) or QTS 4.5.4.2280+ (build 20230112+); QuTS hero h5.0.1.2277+ (build 20230112+) or h4.5.4.2374+ (build 20230417+); QuTScloud c5.0.1.2374+

  1. 1. Identify the current QNAP system type (QTS, QuTS hero, or QuTScloud) and its current version via the system dashboard
  2. 2. For QTS users: Upgrade to QTS 5.0.1.2277 build 20230112 or later, OR QTS 4.5.4.2280 build 20230112 or later
  3. 3. For QuTS hero users: Upgrade to QuTS hero h5.0.1.2277 build 20230112 or later, OR QuTS hero h4.5.4.2374 build 20230417 or later
  4. 4. For QuTScloud users: Upgrade to QuTScloud c5.0.1.2374 or later
  5. 5. Perform the upgrade via Control Panel > System > Firmware Update, or download the update from www.qnap.com/support
  6. 6. After upgrade, verify the new version and build number are applied
Caveat Standard QNAP firmware upgrade risks apply - ensure backups of critical data exist before performing system firmware updates

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-27600 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