dbcve.org
QtsOperating system · Qnap

CVE-2023-51368

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to launch a denial-of-service (DoS) attack via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.6.2722 build 20240402 and later QuTS hero h5.1.6.2734 build 20240414 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 NULL pointer dereference vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated users to trigger a denial-of-service condition via network requests, resulting in system crash or unavailability.

MitigationApply QTS firmware version 5.1.6.2722 (build 20240402) or later for QTS systems, and QuTS hero h5.1.6.2734 (build 20240414) or later for QuTS hero systems.

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= 5.1.4.2596= 5.1.5.2645= 5.1.5.2679
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= h5.1.4.2596= h5.1.5.2647= h5.1.5.2680

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 your QNAP OS type
    Log into the QNAP admin web interface. Look at the top bar or System Information page to determine if the system is running QTS or QuTS hero. The OS name is displayed on the login page or in the dashboard.
    Affected if The system is running QTS or QuTS hero (other QNAP OS variants are not affected by this CVE)
  2. Check QTS firmware version
    Navigate to Control Panel > System Settings > Firmance Update, or go to the Dashboard. The firmware version and build number are displayed (format: 5.1.x.xxxx). Record the full build number.
    Affected if Running QTS version 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, 5.1.4.2596, 5.1.5.2645, or 5.1.5.2679
  3. Check QuTS hero firmware version
    Navigate to Control Panel > System Settings > Firmance Update, or check the Dashboard. The firmware version starts with 'h5.1.x.xxxx' format for QuTS hero. Record the full build number.
    Affected if Running QuTS hero version 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, h5.1.4.2596, h5.1.5.2647, or h5.1.5.2680

You are affected if your QNAP device runs QTS or QuTS hero with a build number matching one of the specific versions listed in the affected products (exact version match required, not a range).

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

Apply QTS firmware version 5.1.6.2722 (build 20240402) or later for QTS systems, and QuTS hero h5.1.6.2734 (build 20240414) or later for QuTS hero systems.

Recommended fix High confidence

QTS 5.1.6.2722 (build 20240402) or later; QuTS hero h5.1.6.2734 (build 20240414) or later

  1. Identify your current QTS or QuTS hero version in the system dashboard
  2. Back up all critical data before initiating firmware upgrade
  3. Navigate to Control Panel > System > Firmware Update (or similar QNAP update mechanism)
  4. Check for and install the recommended update: QTS 5.1.6.2722 (build 20240402) or later for QTS systems
  5. For QuTS hero systems, install h5.1.6.2734 (build 20240414) or later
  6. After upgrade, verify the new firmware version is installed and the system is operational
Caveat QNAP firmware upgrades may have compatibility implications with existing apps; review QNAP app compatibility lists before upgrading

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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