dbcve.org
QtsOperating system · Qnap

CVE-2023-45044

HIGH · 7.2 CVSS v3.1 Published 2024-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 buffer copy without checking size of input vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated administrators to execute code via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.4.2596 build 20231128 and later QuTS hero h5.1.4.2596 build 20231128 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

Buffer copy without size checking vulnerability in QNAP NAS operating systems allows authenticated administrators to achieve remote code execution via network. The vulnerability stems from improper bounds checking in input handling.

MitigationUpdate affected QNAP devices to QTS 5.1.4.2596 build 20231128 or later, or QuTS hero h5.1.4.2596 build 20231128 or later. Restrict administrator access to trusted personnel until patched.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/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 QNAP device OS type
    Log into the QNAP admin console and navigate to Control Panel > System > Firmware or check the dashboard for the OS name (QTS or QuTS Hero)
    Affected if Device is running QTS or QuTS Hero
  2. Check QTS version
    In QTS, go to Control Panel > System > Firmware > Firmware Version to view the exact build number (for example: 5.1.0.2348)
    Affected if Installed QTS version matches any of these builds: 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
  3. Check QuTS Hero version
    In QuTS Hero, go to Control Panel > System > Firmware > Firmware Version to view the exact build number (for example: h5.1.0.2409)
    Affected if Installed QuTS Hero version matches any of these builds: 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
  4. Confirm administrator access exists
    Navigate to Control Panel > System Administration > Administrator to verify if administrator accounts are configured and accessible via network (the vulnerability requires authenticated administrator)
    Affected if Remote administrator login is enabled and accessible on the network

You are affected if your QNAP device runs QTS or QuTS Hero and the installed version matches one of the specific affected builds listed above, with remote administrator access enabled.

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

Update affected QNAP devices to QTS 5.1.4.2596 build 20231128 or later, or QuTS hero h5.1.4.2596 build 20231128 or later. Restrict administrator access to trusted personnel until patched.

Recommended fix High confidence

QTS 5.1.4.2596 build 20231128 or later; QuTS hero h5.1.4.2596 build 20231128 or later

  1. 1. Log into the QNAP admin interface and navigate to Control Panel > System > Firmware Update to check the current QTS or QuTS hero version
  2. 2. Verify if the installed version is one of the affected versions: QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, or 5.1.0.2444; or QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, or h5.1.0.2466
  3. 3. If running an affected version, create a full backup of all critical data stored on the NAS
  4. 4. In the Firmware Update section, check for available updates and ensure the system can upgrade to QTS 5.1.4.2596 (build 20231128 or later) or QuTS hero h5.1.4.2596 (build 20231128 or later)
  5. 5. Apply the firmware update following QNAP's standard upgrade procedure
  6. 6. After the update completes, verify the new firmware version is 5.1.4.2596 build 20231128 or later for QTS, or h5.1.4.2596 build 20231128 or later for QuTS hero
  7. 7. Confirm the vulnerability is remediated by verifying the build date is 20231128 or later
Caveat Standard QNAP firmware upgrade risks apply: ensure power stability during update, review compatibility notes for your specific QNAP model, and back up data before proceeding

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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