dbcve.org
QtsOperating system · Qnap

CVE-2023-45036

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 NAS operating systems where a buffer copy operation lacks proper size validation of input data. When exploited, an authenticated administrator can achieve remote code execution through the network, potentially gaining full control of the affected device.

MitigationUpgrade QNAP devices to QTS 5.1.3.2578, QuTS hero h5.1.3.2578, or QuTScloud c5.1.5.2651 or later. Since this requires authenticated administrator access, enforce strong admin credentials and restrict administrative network access to trusted sources.

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 QNAP product type
    Access the QNAP admin web interface and check the dashboard or System Settings to determine if the device runs QTS, QuTS Hero, or QuTScloud. Alternatively, log in via SSH and run the command `getcfg System Version` to retrieve the system version which indicates the product type.
    Affected if The device is any of the three products (QTS, QuTS Hero, or QuTScloud)
  2. Check installed QTS version
    In the QNAP admin web interface, go to Control Panel > System Settings > Firmware Update to view the current QTS version. Alternatively, run the command `getcfg system version` via SSH.
    Affected if The installed version is 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 installed QuTS Hero version
    In the QNAP admin web interface, navigate to Control Panel > System Settings > Firmware Update to view the current QuTS Hero version (typically displayed with 'h' prefix). Alternatively, run the command `getcfg system version` via SSH which will show a version starting with 'h'.
    Affected if The installed version is 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 installed QuTScloud version
    In the QNAP admin web interface (QuTScloud virtual appliance), go to Control Panel > System Settings > Firmware Update to view the current QuTScloud version. Alternatively, run the command `getcfg system version` via SSH which will show a version starting with 'c'.
    Affected if The installed version is c5.1.0.2498
  5. Confirm administrative access exposure
    Determine if the QNAP admin interface (port 8080 or 443) is exposed to untrusted networks or if weak administrator credentials are in use, since exploitation requires authenticated administrator access.
    Affected if The admin interface is accessible from untrusted networks or administrator credentials are weak or compromised

The environment is affected if the device runs QTS, QuTS Hero, or QuTScloud and the installed version matches one of the specific versions listed in the affected products, combined with the possibility of administrative access being obtainable by an attacker.

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

Upgrade QNAP devices to QTS 5.1.3.2578, QuTS hero h5.1.3.2578, or QuTScloud c5.1.5.2651 or later. Since this requires authenticated administrator access, enforce strong admin credentials and restrict administrative network access to trusted sources.

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) by logging into the QNAP admin interface
  2. 2. Navigate to Control Panel > System > Firmware Update to check the current installed version
  3. 3. For QTS systems: Upgrade to version 5.1.3.2578 (build 20231110) or later
  4. 4. For QuTS hero systems: Upgrade to version h5.1.3.2578 (build 20231110) or later
  5. 5. For QuTScloud systems: Upgrade to version c5.1.5.2651 or later
  6. 6. Use the built-in QNAP Firmware Update utility (Control Panel > System > Firmware Update > Check for Update) or manually download the correct firmware from downloads.qnap.com
  7. 7. After upgrade, verify the new version is installed and the vulnerability is patched
Caveat Review QNAP release notes for QTS 5.1.3/QuTS hero h5.1.3/QuTScloud c5.1.5 for any breaking changes before upgrading; ensure backup of critical data is performed

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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