dbcve.org
QtsOperating system · Qnap

CVE-2023-41273

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 heap-based buffer overflow 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.2.2533 build 20230926 and later QuTS hero h5.1.2.2534 build 20230927 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

A heap-based buffer overflow vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems allows authenticated administrators to achieve remote code execution via network. The overflow occurs in an unspecified component of the QNAP OS, enabling privilege escalation from admin-level access to arbitrary code execution.

MitigationApply the available security updates: QTS 5.1.2.2533 build 20230926+, QuTS hero h5.1.2.2534 build 20230927+, or QuTScloud c5.1.5.2651+. Until patching is possible, restrict administrative interface access to trusted IP addresses only and disable remote administration over untrusted networks.

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
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
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 OS product variant
    Log into the QNAP admin interface and check the System Information page to determine if the system is running QTS, QuTS hero, or QuTScloud. Alternatively, run 'getsysinfo' or check '/etc/config/.qpkg/QuTShero' to identify the OS variant.
    Affected if The system is running QTS, QuTS hero, or QuTScloud
  2. Determine the installed build version
    In the QNAP admin interface, go to Control Panel > System > System Information > System Status to view the exact build version and build date. From CLI, run 'cat /etc/version' or 'cat /proc/version' to retrieve the build number.
    Affected if The installed build matches any of the affected versions listed for the product (QTS = 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; QuTS hero = h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1.2.2534; QuTScloud = c5.1.0.2498)
  3. Verify administrator access status
    Check if there are any administrator accounts configured and whether you have administrative credentials. Review user accounts in Control Panel > Privilege > Users > Administrator. From CLI, examine '/etc/config/passwd' for admin-level accounts.
    Affected if An authenticated administrator account exists and is accessible, which is required to exploit this vulnerability
  4. Confirm network exposure of admin interface
    Check if the QNAP admin web interface (port 8080 or 443) is exposed to network access. Review router/firewall rules and QNAP's QuickerOnline or myQNAPcloud settings. Check Control Panel > System > Network > TCP/IP for listening interfaces.
    Affected if The administrative interface is reachable over the network from untrusted sources (the vulnerability is exploitable via network by authenticated admins)

The system is affected if it runs QTS, QuTS hero, or QuTScloud and matches any of the specific build versions listed (5.1.0.x, 5.1.1.x, 5.1.2.x ranges on QTS/QuTS hero, or c5.1.0.2498 on QuTScloud) AND has an authenticated administrator who can access the admin interface over the network.

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 the available security updates: QTS 5.1.2.2533 build 20230926+, QuTS hero h5.1.2.2534 build 20230927+, or QuTScloud c5.1.5.2651+. Until patching is possible, restrict administrative interface access to trusted IP addresses only and disable remote administration over untrusted networks.

Recommended fix High confidence

QTS 5.1.2.2533 (build 20230926)+, QuTS hero h5.1.2.2534 (build 20230927)+, or QuTScloud c5.1.5.2651+ depending on product

  1. 1. Log in to the QNAP admin interface as an administrator.
  2. 2. Navigate to Control Panel > System > Firmware Update.
  3. 3. Check the current QTS/QuTS hero/QuTScloud version under System Information to confirm it is an affected version.
  4. 4. If using QTS, update to version 5.1.2.2533 (build 20230926) or later.
  5. 5. If using QuTS hero, update to version h5.1.2.2534 (build 20230927) or later.
  6. 6. If using QuTScloud, update to version c5.1.5.2651 or later.
  7. 7. Verify the update completed successfully and the new version is reflected in System Information.
Caveat Review QNAP release notes for any feature changes or migration considerations 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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