CVE-2022-27600
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 · uneditedAn 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 confidenceUncontrolled 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.
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>= 4.5.1, < 4.5.4.2280>= 5.0.0, < 5.0.1.2277= 4.5.4.2280= 5.0.1.2277>= h4.5.1, < h4.5.4.2374>= h5.0, < h5.0.1.2277= h4.5.4.2374= h5.0.1.2277>= c5.0.1, < c5.0.1.2374CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the QNAP product typeLog 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.
-
Determine the installed firmware versionIn 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.
-
Compare QTS version against affected rangesIf 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.
-
Compare QuTS hero version against affected rangesIf 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.
-
Compare QuTScloud version against affected rangesIf 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.
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 · scoped4.5.4.22805.0.1.2277
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.
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. Identify the current QNAP system type (QTS, QuTS hero, or QuTScloud) and its current version via the system dashboard
- 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. 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. For QuTScloud users: Upgrade to QuTScloud c5.0.1.2374 or later
- 5. Perform the upgrade via Control Panel > System > Firmware Update, or download the update from www.qnap.com/support
- 6. After upgrade, verify the new version and build number are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27600 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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