dbcve.org
QtsOperating system · Qnap

CVE-2023-45037

HIGH · 7.2 CVSS v3.1 Published 2024-02-02
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.3.2578 build 20231110 and later QuTS hero h5.1.3.2578 build 20231110 and later QuTScloud c5.1.5.2651 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

This is a buffer overflow vulnerability in QNAP operating systems where a buffer copy operation does not properly validate input size. When exploited by an authenticated administrator, it allows remote code execution via network. The vulnerability stems from missing size validation during memory copy operations.

MitigationUpdate QNAP devices to the fixed versions: QTS 5.1.3.2578 build 20231110, QuTS hero h5.1.3.2578 build 20231110, or QuTScloud c5.1.5.2651 and later. Ensure change management procedures are followed and validate system functionality post-update.

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
QutscloudOperating system
Affected:= c5.1.0.2498

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 the QNAP firmware type
    Log into the QNAP device and navigate to Control Panel > System > Firmware Update, or run `getconf -a | grep -i model` via SSH to identify whether the device runs QTS, QuTS Hero, or QuTScloud.
    Affected if The device runs QTS, QuTS Hero, or QuTScloud.
  2. Check the QTS version and build number
    In the QNAP web interface, go to Control Panel > System > Firmware Update > Firmware Information. Alternatively, run the command `cat /etc/config/defunct/0/boot_image_version` or check the System Overview page for the exact build version (e.g., 5.1.0.2348).
    Affected if The installed 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, or 5.1.3.2578.
  3. Check the QuTS Hero version and build number
    In the QuTS Hero web interface, navigate to Control Panel > System > Firmware Update > Firmware Information, or run `cat /mnt/HDA_ROOT/update/boot.conf` via SSH to extract the exact build version (e.g., h5.1.0.2409).
    Affected if The installed 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, or h5.1.3.2578.
  4. Check the QuTScloud version and build number
    In the QuTScloud interface, go to Control Panel > System > Firmware Update > Firmware Information, or run `cat /etc/version` via SSH to retrieve the build number.
    Affected if The installed version matches build c5.1.0.2498.
  5. Confirm administrator access to the device
    Verify that the account used to manage the QNAP device has administrator privileges. This vulnerability requires an authenticated administrator to exploit the buffer overflow.
    Affected if The device is running an affected build and the attacker would need valid administrator credentials.

A user is affected if their QNAP device runs QTS, QuTS Hero, or QuTScloud and the installed build number matches any of the specific versions listed in the affected products 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

Update QNAP devices to the fixed versions: QTS 5.1.3.2578 build 20231110, QuTS hero h5.1.3.2578 build 20231110, or QuTScloud c5.1.5.2651 and later. Ensure change management procedures are followed and validate system functionality post-update.

Recommended fix High confidence

QTS 5.1.3.2578 (build 20231110) or later; QuTS hero h5.1.3.2578 (build 20231110) or later; QuTScloud c5.1.5.2651 or later

  1. 1. Identify the QNAP product type (QTS, QuTS hero, or QuTScloud) and current version by accessing the QNAP admin console and checking System Administration > Firmware.
  2. 2. Confirm the current version matches one of the affected versions: QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, or 5.1.0.2444; QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, or h5.1.0.2466; QuTScloud c5.1.0.2498.
  3. 3. Back up all critical data and system configurations before performing the upgrade.
  4. 4. Navigate to Control Panel > System > Firmware Update and check for the latest available version.
  5. 5. For QTS: Upgrade to version 5.1.3.2578 (build 20231110) or later.
  6. 6. For QuTS hero: Upgrade to version h5.1.3.2578 (build 20231110) or later.
  7. 7. For QuTScloud: Upgrade to version c5.1.5.2651 or later.
  8. 8. After upgrade, verify the new version is installed and confirm the vulnerability is resolved.
Caveat Standard QNAP NAS upgrade considerations apply: ensure application compatibility with new QTS/QuTS version, review release notes for known issues, and verify backups are complete before proceeding

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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